Integrated communications network for transactions

ABSTRACT

An integrated communications network may be integrated with existing payment systems to provide for more efficient and secure payment related communications. The integrated communications network may use mobile network protocol encapsulation to provide more efficient, faster, and more robust payment related communications to a payment processor across a mobile network. The integrated communications network may implement a location-aware network communications system that may allow a payment processor to obtain additional information about a consumer using a location-aware header of a network communication.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a divisional application of U.S. application Ser.No. 16/389,764 titled “INTEGRATED COMMUNICATIONS NETWORK FORTRANSACTIONS”, filed Apr. 19, 2019, which is a divisional application ofU.S. application Ser. No. 14/173,718, titled “INTEGRATED COMMUNICATIONSNETWORK FOR TRANSACTIONS”, filed Feb. 5, 2014, which is anon-provisional application of and claims the benefit of priority ofU.S. Provisional Application No. 61/818,824, titled, “COMMUNICATIONNETWORK INFRASTRUCTURE,” filed on May 2, 2013; U.S. ProvisionalApplication No. 61/818,812, titled, “INTEGRATED COMMUNICATION NETWORKINFRASTRUCTURE,” filed on May 2, 2013; and U.S. Provisional ApplicationNo. 61/761,185, titled, “INFRASTRUCTURE UTILIZING MOBILE CARRIERSYSTEM,” filed on Feb. 5, 2013; all of which are herein incorporated byreference in their entirety for all purposes.

BACKGROUND

The widespread availability of mobile networks throughout variousregions provides a readily available communications network forinitiating and processing transactions throughout various rural,undeveloped, and even developed regions. For example, in some regions,there may not be sufficient payment processing infrastructure betweenconsumers, merchants, acquirers, issuers, and payment processingnetworks to allow for established and traditional payment processingnetworks to operate. However, such regions typically have some mobilenetwork infrastructure. Accordingly, existing mobile networkinfrastructure can be better leveraged to process payment andnon-payment transactions.

Current implementations of using mobile networks for initiating andprocessing transactions are limited for a number of reasons. Forexample, in some solutions, a payment processor may work with mobilenetwork operators to install hardware and/or software in each of amobile network operator's base stations in order to use the mobilenetwork to facilitate transactions for an established payment processingnetwork. However, installing payment processing-specific networkhardware at each base station of a mobile network requires significantinfrastructure investment and maintenance. Since a payment processor maynot necessary have direct access to the base stations, maintenance andmonitoring of the installed hardware can be difficult, which raisesreliability concerns. Furthermore, the hardware and/or software may belimited in bandwidth and processing speeds.

In other solutions, a mobile network operator and the payment processingnetwork may coordinate with third party service providers (e.g., a thirdparty IP conversion provider) in order to process transactions receivedon their mobile networks. Typically, third party service providersconvert mobile communication messages to internet protocol messages onbehalf of the payment processing networks and submit messages to thepayment processing network to process transactions. After processing thetransaction, the payment processing network may then return the messagethrough the third party service provider, mobile network operator,issuer, and/or acquirer in order to complete the transaction. However,this process can be expensive, inefficient, slow, and complex as itrequires a middle entity to manage and process transactions. Thesesolutions may be also inefficient and costly as the payment processormay not have direct control of the third party equipment, and the datatransmission may be limited by the size of the data packets configuredto be processed by the communications network.

Therefore, there is a need for a mobile payment system to betterleverage existing telecommunications infrastructure in a more efficient,reliable, and integrated manner to overcome the limitations of existingsystems.

Further, the development and wide adoption of powerful mobilecommunications devices by consumers has provided mobile networkoperators, device manufacturers, and other mobile service providers witha large amount of consumer information that may not be directlyavailable to transaction processors. Payment processing networks andother payment systems developed largely before the emergence andadoption of such powerful mobile communications devices used byconsumers. Due to the large investment required to integrate mobiledevices into existing payment transaction processing flows, much of theadditional information that mobile devices can provide have not beenintegrated into payment systems and those payment systems that haveintegrated such information, have not done so at the networkcommunications protocol level.

Therefore, there is a need for an integrated communications network thatis capable of integrating existing payment systems with the uniqueinformation available from the ubiquitous use of mobile devices byconsumers.

Embodiments of the invention address the above problems, and otherproblems, individually and collectively.

SUMMARY

Embodiments of the invention are directed to a method comprisingreceiving, by a mobile switching center associated with a first mobilenetwork, a transaction request message from a computing devicecommunicating with a second mobile network. The transaction requestmessage may be received via a switch configured to connect a pluralityof mobile networks. In such embodiments, the second mobile network maybe remote from the first mobile network and local to the computingdevice. The method further comprises converting the transaction requestmessage from a first protocol to a second protocol by a protocolconversion module. The converted transaction request message may be sentto a payment processing server, and the payment processing server mayprocess a transaction associated with the converted transaction requestmessage. The method further comprises receiving a transaction responsemessage from the payment processing server, converting the transactionresponse message from the second protocol to the first protocol, andsending the converted transaction response message to the computingdevice via the switch.

Another embodiment of the invention is directed to a computer comprisinga processor, and a computer readable medium coupled to the processor,the computer readable medium comprising code, executable by theprocessor for implementing a method. The method comprises receiving, bya mobile switching center associated with a first mobile network, atransaction request message from a computing device communicating with asecond mobile network. The transaction request message may be receivedvia a switch configured to connect a plurality of mobile networks. Insuch embodiments, the second mobile network may be remote from the firstmobile network and local to the computing device. The method furthercomprises converting the transaction request message from a firstprotocol to a second protocol by a protocol conversion module. Theconverted transaction request message may be sent to a paymentprocessing server, and the payment processing server may process atransaction associated with the converted transaction request message.The method further comprises receiving a transaction response messagefrom the payment processing server, converting the transaction responsemessage from the second protocol to the first protocol, and sending theconverted transaction response message to the computing device via theswitch.

Another embodiment of the invention is directed to a method comprisingreceiving a network protocol packet including a network protocol headerand a transaction payload. The network protocol header may include alocation-aware header portion, including location-aware data retrievedby a location terminal in proximity to a mobile device. The methodfurther comprises parsing the location-aware header portion from thenetwork protocol packet and identifying the location-aware data withinthe location-aware header portion according to a location-aware networkprotocol. The method further comprises retrieving a consumer-targetedmessage from a database based on the location-aware data in thelocation-aware header portion. The method further comprises generating aresponse message including the consumer-targeted message and sending theresponse message including the consumer-targeted message to the mobiledevice.

Another embodiment of the invention is directed to a method comprisingreceiving a network protocol packet including a network protocol headerand a transaction payload. The network protocol header may include alocation-aware header portion, including location-aware data retrievedby a location terminal in proximity to a mobile device. The transactionpayload may include transaction data generated by a point of sale devicefor a transaction. The method further comprises parsing thelocation-aware header portion from the network protocol packet andidentifying location-aware data within the location-aware header portionaccording to a location-aware network protocol. The method furthercomprises performing an authorization process for the transaction usingthe transaction data. The transaction is validated using the data in thelocation-aware header portion. A validation response message isgenerated for the transaction based on the validation, and sent to themobile device.

Another embodiment of the invention is directed to a system comprising aplurality of location terminals configured to retrieve data from amobile device in proximity to one of the plurality of locationterminals, and store the retrieved data in a location-aware headerportion of a network protocol header of a network protocol packet. Thesystem further includes a location proxy device configured to receivethe network protocol packet and store transaction data generated by apoint of sale device into a transaction payload of the network protocolpacket. The system further comprises a server computer configured toreceive the network protocol packet from the location proxy device,perform an authorization process for the transaction using thetransaction data, and process the retrieved data from the location-awareheader portion of the network protocol packet. The server computer isfurther configured to validate the transaction using the retrieved data,generate a validation response message for the transaction based on thevalidation, and send the validation response message to the mobiledevice.

These and other embodiments of the invention are described in furtherdetail below with reference to the Figures and the Detailed Description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an existing system for transferring data received over amobile network from a computing device to a payment processing networkserver computer using local conversion modules at mobile network basestations.

FIG. 2 shows a system diagram for a system configured to transfer datareceived over a mobile network across a mobile network to a paymentprocessing network mobile network according to an embodiment of thepresent invention.

FIG. 3 shows a detailed system diagram for a system configured totransfer data across a mobile network to a payment processing mobilenetwork according to an embodiment of the present invention.

FIG. 4 is a flowchart describing a method of processing a transactionusing a payment processing network mobile network according to anembodiment of the present invention.

FIG. 5 show a transaction processing system with location-awareinfrastructure according to one embodiment of the present invention.

FIG. 6 shows a detailed system diagram for a transaction system withlocation-aware infrastructure according to an embodiment of the presentinvention.

FIG. 7 shows a block diagram illustrating the multiple communicationmodes that a mobile device is configured to use in an exemplarylocation-aware transaction processing system according to an embodimentof the invention.

FIG. 8 shows a block diagram illustrating the interaction of multiplelocation-aware infrastructure devices and mobile devices in an exemplarylocation-aware transaction processing system according to an embodimentof the invention.

FIG. 9 shows a diagram of a network protocol packet according to anexemplary embodiment of the invention

FIG. 10 shows a detailed diagram of the data flow using an exemplarylocation-aware infrastructure according to an embodiment of theinvention.

FIG. 11 is a flowchart describing an exemplary method of using alocation-aware infrastructure to track a consumer and issue aconsumer-targeted message to a consumer according to an embodiment ofthe invention.

FIG. 12 is a flowchart describing an exemplary method of using alocation-aware infrastructure to validate a transaction according to anembodiment of the invention.

FIG. 13 shows a block diagram of a computer apparatus according to anembodiment of the invention.

DETAILED DESCRIPTION

Embodiments of the invention are directed at methods, systems, andapparatuses for providing an integrated communications network that maybe integrated with existing payment systems to provide for faster, moreefficient, smarter (i.e., more secure), and more flexible paymentrelated communications systems. The integrated communications networkmay include at least two distinct but related concepts that allow theintegrated communications system to implement higher throughput, moresecure, and more flexible payment systems. First, some embodiments ofthe integrated communications network may use mobile network protocolencapsulation to use existing telecommunications infrastructure toprovide faster, more efficient, and more robust payment communicationsacross mobile networks. Second, some embodiments of the integratedcommunications system may include location-aware capabilities that mayallow a payment processor to obtain additional information about aconsumer that existing payment systems may not have direct access to,and pass the additional information using a location-aware header of anetwork communication to provide additional consumer authentication,consumer-targeted information, or any other relevant applications usingthe additional data.

First, as described above, some embodiments of the integratedcommunications network may use mobile network protocol encapsulation toprovide more efficient, faster, and more robust payment relatedcommunications to a payment processor across a mobile network. Forexample, a payment processor may become operator of mobile networkinfrastructure in order to gain access to out-of-band signaling channelcapabilities associated with mobile networks. The out-of-band signalingchannel (e.g., an out-of-band control signaling channel) may beout-of-band from the voice data channel associated with mobile networks,and may be traditionally used to control the setup and break down ofend-to-end voice telecommunication messages. In embodiments of thepresent invention, the out-of-band signaling channel may be used to passtransaction data for more efficient, higher throughput, and morereliable payment solutions using mobile communication networks.

In some embodiments of the present invention, the payment processor mayissue subscriber identifiers and/or secure modules with such subscriberidentifiers (e.g., device identifiers stored on SIM cards) to computingdevices involved in payment transactions to allow the computing devicesto access mobile communication networks. The computing devices may thenuse their subscriber identifiers for authentication to the mobilenetworks. In some embodiments, the local mobile network infrastructuremay be able to identify the home mobile switching center associated withthe payment processor and pass data all the way to the mobile switchingcenter associated with the computing device subscriber identifier whilestaying in the mobile or telephony network domain. For example, evenwhen the home mobile switching center is located away from the localmobile network of the computing device, the data can be passed to thehome mobile switching center of the computing device through multiplemobile and/or telephony networks using mobile roaming technology.

The computing devices may be configured to encapsulate payment relatedcommunications originating in a communications protocol (e.g., internetprotocol communications, short message service (SMS), unstructuredsupplementary service data (USSD), ISO, Society for Worldwide InterbankFinancial Telecommunication messages (SWIFT), enhanced messaging service(EMS), multimedia messaging service (MMS), extensible markup language(XML)) into the mobile network protocol (e.g., SS7 communications orother out-of-band signaling messages), and may pass the payment relatedcommunications encapsulated in the mobile network protocol to thepayment processing network using existing mobile network roaminginfrastructure. By encapsulating the payment related communications intothe mobile network protocol, the payment related communications may bepassed across multiple mobile networks using existing roamingcommunications infrastructure. Once received at a mobile switchingstation associated with the payment processing network, the encapsulatedcommunications can be decapsulated, decoded, or otherwise converted intothe associated payment communication protocol for processing.Accordingly, the mobile switching center associated with the paymentprocessor may have a central protocol conversion module that may beconfigured to perform mobile network protocol (e.g., SS7, etc.) tonon-mobile communications protocol (e.g., Internet Protocol (IP), etc.)conversion, and pass the payment related information in the receivedcommunications to the payment processor for processing. Accordingly,payment communications may be passed more efficiently, robustly, and inhigher throughput to a payment processor using end-to-end mobile networkcommunications via mobile network infrastructure across multiple mobilenetworks. Additionally, the end-to-end mobile network communications donot require local protocol conversion modules integrated into mobilebase stations in order to pass communications to and from paymentprocessing systems.

Second, embodiments of the integrated communications network mayimplement a location-aware network communications system that may allowa payment processor to obtain additional information about a consumerusing a location-aware header of a network communication. Theinformation passed in the location-aware header may allow the paymentprocessor the ability to provide more effective authentication of aconsumer during a transaction and provide additional fraud analysis,consumer-targeted information (e.g., advertisements, coupons, alerts,etc.), and other applications relevant to a payment process. Forexample, a location-aware network header may include a merchantidentifier (e.g., a unique identifier associated with a merchant,service provider, government entity, or any other registered party), alocation identifier (e.g., a particular merchant's store location, alocation within a merchant's store, etc.), a mobile device identifier(e.g., a hardware identifier for the mobile device, a phone number, adevice manufacturer serial number, etc.), a consumer identifier (e.g., asubscriber identifier, a mobile wallet identifier, a payment accountuser name, a phone number, etc.), and/or a transaction type indicator(e.g., tracking, payment transaction, etc.), or any combination thereof.The location-aware network header may allow a payment processor toobtain direct access to additional information about the consumer and/ormerchant in order to better authenticate consumers and transactions aswell as better predict consumer behavior and target consumers foradvertising and management services. In some embodiments, thisadditional information can be made available to a payment processorwithout requiring the consumer to conduct a transaction.

Furthermore, the location-aware header may be integrated with existingpayment systems by incorporating the location-aware information into anetwork communication protocol header instead of in a transactionpayload. For example, the location-aware header may be transmitted inthe network protocol header along with an existing payment message(e.g., ISO 8583 standard payment authorization request message) as thepayload to a payment processor that may parse the information in thelocation-aware header message before processing the existing paymentmessage in the payload using existing transaction processing systems.The payment processor may then use the additional information providedin the location-aware header to further authenticate and validate thetransaction. Accordingly, embodiments may be incorporated into existingpayment systems at the network communication protocol level withoutrequiring different payment standards and authorization systems.

Additionally, in some embodiments, the location-aware header informationmay be used with other types of transaction payload. For example, thetransaction payload may include mobile communications, broadcastcommunications (e.g., television, radio, satellite, etc.), or otherprotocol specific device-to-device communications. In some embodiments,the integrated communication network infrastructure may capturetransactions that are initiated through different types of networks suchas payment processing networks (e.g., via point of sale devices orEuropay®, MasterCard® and Visa® (EMV) devices), mobile networks (e.g.,via mobile or portable computing devices), internet (e.g., via computingdevices such as desktops, laptops, etc.), as well as through televisionnetworks, or any types of communication infrastructure.

Embodiments of the present invention may consolidate various transactionstandards into a single enhanced standard that can process transactionsoriginating through any of these channels/networks, rather than usingdifferent individual processing standards required for differentnetworks. This enhanced standard may use the location-aware header toprovide enhanced data processing and analysis, including increasedconsumer location tracking capabilities, increased information aboutconsumer behavior, and enhanced consumer authentication and frauddetection. Through these improvements, the integrated platform providesmerchants with more value by improving the volume of transactions that amerchant may process, thus leading to potentially more revenue for amerchant. The location-aware header also may improve the amount oftransactions that the network may process by expanding theinfrastructure to incorporate different payment protocols and channels(i.e., internet, proprietary or existing payment processing protocols,mobile communication networks protocols (e.g., SS7), televisionprotocols, etc.).

A detailed explanation of each of the above described integratedcommunication network capabilities are described separately below.However, note that both network capabilities may be incorporated into asingle integrated communication system that allows a payment processorto receive location-aware transaction information using thelocation-aware network headers and distribute alerts, incentives, andany other relevant information across mobile network infrastructure tomobile devices (and other computing devices) using mobile networkprotocol encapsulation.

I. Mobile Network Protocol Encapsulation

Embodiments of the present invention are directed to systems,apparatuses, and methods of implementing an out-of-band signalingchannel (e.g., out-of-band control signaling channel such as SS7communications protocol, etc.) payment network architecture using acentralized payment processing network incorporating both mobile networkoperator functionality and payment processing capabilities. For example,in some embodiments of the present invention, a payment processingnetwork (e.g., Visa™) may implement a protocol conversion module that iscapable of converting messages received over an out-of-band signallingchannel (e.g., an SS7 protocol) to be transmitted over the Internet viaan internet protocol (IP).

In some embodiments of the prevent invention, the conversion may beperformed by a stream control transmission protocol (SCTP). The streamcontrol transmission protocol may be configured to identify an internetprotocol message encapsulated within an SS7 protocol message, and todecapsulate the message received using an SS7 protocol back into aninternet protocol message. The message may be sent as part of processinga transaction or to convey a data message to the payment processingnetwork or to another user using an out-of-band signaling channelassociated with a mobile network. Accordingly, the protocol conversionmodule may facilitate the integration of a mobile network and aninternet protocol based payment processing network into a single entitythat may be able to direct, convert, process, and communicate acrossmultiple networks using both mobile network protocols (e.g., SS7out-of-band signaling channel communications protocols) and IPprotocols.

For example, in some regions, there may not be sufficient paymentprocessing infrastructure between consumers, merchants, issuers, andpayment processing networks to allow for established and traditionalpayment processing networks to operate. For example, merchants in somerural areas may not have network connectivity to process cardtransactions. However, such regions typically have some mobile networkinfrastructure. Accordingly, transactions may be processed using mobilenetworks by implementing SS7 communications protocols to passtransaction information across the mobile network infrastructure to acentral mobile network associated with a payment processing network forprocessing. SS7 communications protocol stands for Signaling System No.7 and is a standard followed by mobile network operators around theworld.

According to embodiments of the present invention, a payment processingnetwork (e.g., Visa®) may incorporate the functionality of a mobilenetwork operator into the central payment processing systems in order toprovide an end-to-end transaction processing system that may operateacross both an IP protocol as well as mobile network protocols, such asSS7. Accordingly, a payment processing network may provide transactionprocessing and routing services across multiple networks and throughoutvarious regions domestically or around the world from a central locationwithout requiring payment processing network infrastructure to be placedon each base station, as depicted in FIG. 1.

For example, in some embodiments of the present invention, a paymentprocessing network (e.g., a payment processor) may obtain cellularspectrum in a geographical region and become a registered mobile networkoperator. Because the payment processing network is registered as amobile network operator (i.e., telecommuncations provider) and mayprovide services to cellular network subscribers, the payment processingnetwork may gain access to SS7 signaling infrastructure.

Once the payment processing network has access to the SS7infrastructure, the payment processing network may use the signalinginfrastructure to encapsulate, transmit, receive, convert, and/orprocess transactions (and other data messages) from around the world ata central location via mobile networks. In some embodiments, the paymentprocessing network may provide a subscriber identifier for a computingdevice (e.g., a subscriber identifier stored in a SIM card, securememory element, or other types of secure module, etc.), and may use thesubscriber identifier to send and receive transaction communications,notifications, alerts, coupons, rewards, etc. over a mobile networkcommunications infrastructure. The payment processing network may useexisting mobile network roaming infrastructure to identify andcommunicate with devices communicating over multiple mobile networksanywhere in the world in a more efficient, effective, and faster manner.

In addition, using embodiments of the present invention, the paymentprocessing network can avoid using a third party IP protocol conversionservice and instead convert all of the transaction messages using aprotocol conversion module at the payment processing network mobilenetwork. Therefore, instead of the payment processing network having toinstall hardware or software upgrades into mobile network operators'local base stations throughout the world, the payment processing networkmay have a roaming agreement with the mobile network operators to routeend-to-end transactions between users, merchants, and any otherconfigured devices to the payment processing network using the roamingcapabilities of the mobile network infrastructure. The transactionmessages received in the mobile network protocol format at the paymentprocessing network can then be converted to an internet protocol toallow components of the payment processing network to process thetransaction via internet protocol. After processing, the paymentprocessing network may then reverse the transaction flow and return atransaction authorization or transaction completion message back to theconsumer, a merchant associated with the transaction, a mobile networkoperator associated with the consumer, etc. The return message may beencapsulated within the mobile network protocol (e.g., SS7) prior tobeing sent back through the mobile network.

A. Definitions

Prior to discussing embodiments of the invention, descriptions of someterms may be helpful in understanding embodiments of the invention.

The term “mobile network” may refer to any type of wireless network thatallows for communication between devices. Each mobile network may beserved by at least one fixed-location transceiver (e.g., a base station)that covers a particular geographic region. A mobile network may includea plurality of base stations, allowing communications between mobiledevices and computing devices moving through the geographic regionserved by the plurality of base stations. Communications between basestations may be accomplished by sending voice or data informationthrough a mobile switching center that is communicatively coupled withthe base stations. Mobile networks allow mobile devices and computingdevices to be connected to a switch (e.g., a public switched telephonenetwork (PSTN)) in order to provide telephone and other network serviceswith other mobile devices and computing devices located on other mobilenetworks. Each mobile network may be owned and operated by a differentmobile network operator (e.g., telecommunications service provider) thatprovides services (e.g. voice and data communications) for users anddevices that are subscribed to the mobile network operator's mobilenetwork. A computing device that is subscribed to the mobile network mayhave a unique subscriber identifier provisioned on a secure module(e.g., SIM card) associated with the computing device. For example, theunique subscriber identifier can be provisioned on a hardware componentof the computing device (e.g., a SIM card, a secure module, etc.).

The term “base station” may refer to a device that may facilitatecommunications across mobile networks. The base station is typicallyinstalled at a fixed location and may contain: equipment fortransmitting and receiving voice and/or data signals (e.g.,transceivers), antennas, and equipment for encrypting and decryptingcommunications with a base station controller (BSC). Base stations maybe used by mobile networks to facilitate communications between mobiledevices. The base station may also be referred to as a base transceiverstation (BTS). Base station controllers may be configured to control oneor more BTS, and provide the functionality of managing the network,handover management and call setup.

The term “mobile switching center” may refer to a device configured forrouting data and signals. The mobile switching center (MSC) may beresponsible for routing voice calls, short message service (SMS)messages, and other data through a mobile network. The mobile switchingcenter may also be configured to set-up and release end-to-endconnections. The mobile switching center may also be configured tohandle handovers between base stations. For example, when a mobiledevice approaches the edge of a region covered by a first base station,the mobile switching center may determine an adjacent base station forhanding over the management and services for the mobile device. A mobilenetwork may include one or more mobile switching centers, typicallybased on the size of the mobile network.

The mobile switching center may also be configured to determine in whichmobile switching center the destination device or system is currentlylocated. Communications between computing device (e.g., mobile phones)are typically routed to a switch (e.g., a global switch or publicswitched telephone network (PSTN)) through the mobile switching center.In some embodiments, some of the functionality of the mobile switchingcenter may be implemented by a separate gateway mobile switching center.In such embodiments, the gateway mobile switching center (GMSC) may becoupled or linked to the mobile switching center.

The term “switch” may refer to a device for receiving and directingcommunications data. For example, the switch may receive data and voicecommunications from a source (e.g., a first mobile network) and directthe communications to a destination (e.g., a second mobile network). Inembodiments of the present invention, the switch may also direct datacommunications sent by a mobile network to a payment processing networkmobile network (e.g., a mobile network operated by a payment processornetwork). An example of a switch is a public switched telephone network,which is an international telephone system that carries data betweennetworks. The switch can be configured to pass both in-bandcommunications data and out-of-band signaling communications. Inembodiments of the present invention, the switch may send and receiveencapsulated transaction messages using the out-of-band signalingchannel.

The term “communicatively couple” may refer to an association betweendevices that allows data to be sent between the devices. For example,communicatively couple may refer to a connection between two mobilenetworks that allows data and voice communications to be transmittedbetween the two mobile networks. In embodiments of the presentinvention, the connection between the two or more mobile networks thatcommunicatively couples the two or more mobile networks may be through aswitch (e.g., a public switched telephone network).

The term “remote” may refer to an association between two devices. Inembodiments of the present invention, remote may refer to when a mobilenetwork is not directly communicating with a computing device. Forexample, when the computing device that is subscribed to a first mobilenetwork (e.g., AT&T™) is communicating with a base station in a secondmobile network (e.g., Verizon™), the computing device may be consideredremote to a first mobile network.

The term “local” may refer to an association between two devices. Inembodiments of the present invention, local may refer to a mobilenetwork that a computing device is presently or currently communicatingwith. For example, when the computing device is communicating directlywith a base station in a second mobile network, the computing device maybe considered local to that base station and local to that second mobilenetwork.

The term “protocol” may refer to a set of standards for formatting adata message or the transmission of message. In embodiments of thepresent invention, protocol may refer to a communications protocol thatmay be used to facilitate communications between two or more mobilenetworks, systems, or devices. Each communications protocol may definerules for the data exchange between computing devices. A protocol may beimplemented as hardware, software, or both. In order for differentsystems and devices to be able to understand data sent between twodevices, communications protocols may be uniform between the partiesinvolved, or the systems may be configured to convert,encapsulate/decapsulate, and/or encode/decode different communicationsprotocols. In embodiments of the present invention, a data message maybe sent from a first mobile network in a first protocol, and the secondmobile network may be required to convert, decapsulate, or decode thedata message into a second protocol to be able to process the datamessage.

The term “converting” may refer to a process of altering datacommunications. For example, in embodiments of the present invention,converting may refer to the process of encapsulating a data message thatis sent in a first protocol within a second protocol. For example, atransaction request message may be generated by a computing device in aninternet protocol. The transaction request message in the internetprotocol may be encapsulated within a mobile network communicationsprotocol (e.g., SS7 communications protocol), which may allow thetransaction request message to be transmitted or sent over traditionalmobile network infrastructure (e.g., from a base station and to a switchvia a mobile switching center). Converting may further refer to theprocess of decapsulating (or decoding) the encapsulated data message toextract the data message in the first protocol from the second protocol.For example, the protocol conversion module may receive the transactionrequest message from the computing device via the switch, anddecapsulate the transaction request message from the mobile networkprotocol (e.g., SS7 communications protocol).

The term “payment processing network mobile switching center” may referto a mobile switching center configured to provide transaction relatedservices. In such embodiments, the payment processing network mayfunction as a mobile network operator. In some embodiments, the paymentprocessing network mobile switching center may combine the functions andservices provided by a traditional mobile network and a paymentprocessing network. In other embodiments, the payment processing networkmobile network may be configured to provide transaction-related servicesand may not provide traditional telecommunications services (e.g., voicecalls between mobile device users).

The term “home location register” may refer to a database storing userdata and device data for a mobile network. The data stored by the homelocation register (HLR) may include a subscriber identifier (e.g., aninternational mobile subscriber identity (IMSI)) and a connectionidentifier associated with the subscriber identifier (e.g., a mobilestation international subscriber directory number (MSISDN)) for eachmobile device or computing device subscribed to the mobile network. Thesubscriber identifier (e.g., IMSI) is used to uniquely identify eachSubscriber Identity Module (SIM) configured for use on the mobilenetwork. The subscriber identifier (e.g., IMSI) may be used as theprimary key for each home location register record. The connectionidentifier (e.g., a MSISDN) may include a telephone number for eachsubscriber device. The home location register (HLR) record for eachsubscriber device may also include the current location of the devicewithin either the mobile network to which the device is subscribed to ora different mobile network. The HLR record for each subscriber devicemay be updated when the SIM associated with the device moves intoanother area covered by a different home location register.

The term “visitor location register” may refer to a database storinguser data and device data for a mobile network. The visitor locationregister (VLR) may be a database of both the subscriber andnon-subscriber computing devices (e.g., mobile devices) that have roamedinto the jurisdiction or coverage area of a mobile switching center(MSC). Typically, the visitor location register only contains the mobiledevices that are currently located in the area covered by the particularmobile switching center the visitor location register is associatedwith. Once a mobile device moves out of the area covered by theparticular mobile switching center (or is inactive for a period oftime), the visitor location register record for the mobile device may bedeleted. The visitor location register may receive the user data anddevice data for a non-subscriber's computing device from the homelocation register (HLR) of the mobile network associated with thenon-subscriber. One function of the visitor location register isminimizing the number of queries that the mobile switching center mustmake to the home location register, which holds permanent data regardingthe mobile network's subscribers.

The term “internet protocol network” may refer to a network configuredto provide communications between computing devices, including mobiledevices. Each computing device within an internet protocol (IP) networkmay use internet protocol for their communications protocol. Computingdevices connected through an IP network each have unique internetprotocol addresses that are used to uniquely identify the computingdevice within the IP network. Data may be sent across the IP networkfrom a source computing device to a destination computing device in datapackets containing control information (e.g., IP addresses ofdestination computing device and source computing device) and data(e.g., message contents).

The term “protocol conversion module” may refer to a module that isconfigured to convert a data message from a first protocol to a secondprotocol. In some embodiments, different mobile networks may utilizedifferent protocols for sending and receiving data. In order to provideinteroperability (e.g., communications) between mobile networksutilizing different protocols, the protocol conversion module may berequired to convert the protocol used by a source computing device tothe protocol used by a destination computing device. The conversion maybe accomplished by encapsulating the data signal in a first protocolinto a second data signal in a second protocol. For example, theprotocol conversion module may encapsulate a data message sent in aninternet protocol within an SS7 protocol message. This may facilitatethe transaction of the data message sent through a mobile networksystem. The protocol conversion module may convert the data message froman SS7 protocol using a stream control transmission protocol toencapsulate the transaction request message within an internet protocolmessage. In some embodiments, the protocol conversion module may not belocated in a base station of the mobile network, and may be a componentin a payment processing network mobile switching center. In otherembodiments, the protocol conversion module may be a separate componentwithin a payment processing network mobile network and be linked to thepayment processing network mobile switching center.

The term “stream control transmission protocol” may refer to a protocolused to encapsulate a data message into a transmission protocol. In someembodiments of the present invention, the stream control transmissionprotocol may be used by the protocol conversion module to encapsulate aninternet protocol message within an SS7 protocol signal so that theinternet protocol message may be passed over one or more mobilenetworks, and be decapsulated and processed at a payment processingnetwork. In other embodiments, the stream control transmission protocolmay be used to encapsulate and decapsulate other message protocolsincluding SMS, USSD, and any other designated communication protocolsthat are understood between two computing devices.

The term “computing device” may refer to device that is configured tosend and receive data messages. For example, the computing devices maysend and receive data messages to conduct a transaction. The computingdevice may be capable of conducting communications over a mobilenetwork. In some embodiments, the computing device may be a subscriberto a mobile network. In such embodiments, the computing device mayinclude a subscriber identity module (SIM) or other secure module orelement that may be provided by the mobile network or by a paymentprocessing network.

A computing device may be in any suitable form. For example, suitablecomputing devices can be hand-held and compact so that it can fit into auser's pocket (e.g., pocket-sized). The computing device can include aprocessor and memory, input devices, and output devices, operativelycoupled to the processor. Specific examples of computing devices includecellular or mobile phones, computer systems configured to communicatewith a mobile network, transaction system access devices, tabletcomputers, personal digital assistants (PDAs), pagers, portablecomputers, smart cards, and other similar devices. Computing devices mayalso be referred to as mobile devices, user devices, mobile stations orsubscriber devices. Computing devices may also be referred to asmerchant computers, point of sale (POS) devices, acquirer computersand/or issuer computers.

In some embodiments, the computing device may comprise a SIM card orother secure module or hardware device that contains a device identifier(e.g., NEI), subscriber identifier (e.g., IMSI), and is associated witha phone number (e.g., MSISDN) provided by a mobile network operator.Depending on the type of mobile network being operated (e.g., CDMA orGSM), the computing device may regularly (e.g., periodically at a veryhigh rate) communicate the relevant identifier information (e.g., IMEI,IMSI, MSISDN) to base stations that track the users connecting to theirtower at any given time in order to allow communication with anycomputing device.

The term “communicating” may refer to the conveyance of data orinformation between devices. For example, communicating may refer to acomputing device or mobile device actively exchanging data andinformation with a base station in a mobile network. Communicating mayalso generally refer to the computing device being located within thecoverage area of a particular base station of the mobile network.

The term “mobile station roaming number” may refer to an identifier usedto route communications between mobile networks. For example, a mobilestation roaming number (MSRN) may be a telephone number used to routetelephone calls in a mobile network from a gateway mobile switchingcenter (GMSC) to the target mobile switching center (MSC) of a secondmobile network where a mobile station (e.g., computing device or mobiledevice) is located. The mobile station roaming number is needed by thehome network to forward incoming communications directed to thecomputing device or mobile device to the second mobile network thecomputing device or mobile device is currently visiting. A visitorlocation register (VLR) may generate the mobile station roaming numberon request from the mobile switching center, and the mobile stationroaming number may also be stored in the home location register (HLR).The mobile station roaming number may contain the current visitorcountry code, the visitor national destination code, the identificationof the current mobile switching center together with the subscribernumber. The mobile station roaming number may also be referred to as a“mobile subscriber roaming number.”

The term “subscriber identifier” may refer to data that may be used touniquely identify a subscriber. The subscriber identifier may be anumeric or alphanumeric value. The subscriber identifier may include twoparts. The first part may be comprised of five or six digits identifyinga network operator in a specific country with whom the subscriber holdsan account. The second part is allocated by the mobile network operatorto uniquely identify the subscriber. Subscriber identity module (SIM)cards, storing the subscriber identifier, can be installed andtransferred between different mobile devices. The SIM information mayalso be stored on a device's general storage memory or may be securedwithin a SIM card emulator on the general memory.

In some embodiments, the subscriber identifier may also be referred toas an international mobile subscriber identifier (IMSI). The IMSI may beused to acquire the details of the mobile device in the home locationregister (HLR) or the visitor location register (VLR). The internationalmobile subscriber identifier (IMSI) may be composed of two parts, amobile network operator identifier and a subscriber identifier. Themobile network operator identifier may be used to identify the mobilenetwork operator in a specific country with whom the subscriber holds anaccount. The subscriber identifier may be used by the mobile networkoperator to uniquely identify the subscriber.

The term “secure module” may refer to a hardware element that securelystores data. The secure module may store any data for a mobile device,including, for example, a device identifier, a consumer identifier, anda consumer credential. The secure module may be associated with a uniqueidentifier established by an entity that issued the secure module. Suchentities may include a mobile device manufacturer, a mobile networkoperator, a payment processing network, or an issuer (e.g., bank). Thesecure module may be embedded within a mobile device. An example of asecure module is a subscriber identifier module (SIM) card. SIM cardscan provide identification, authentication, data storage and applicationprocessing. SIM cards can also be configured to allow a mobile device tosend and receive communications. SIM cards can store network-specificinformation that can be used to authenticate and identify subscribers ona network in order to allow a mobile device access to the network.

The term “message” may refer to any data or information that may betransported from one entity to another (e.g., one mobile/computingdevice to another mobile/computing device). Further, a message mayinclude a single signal or data packet or a combination of multipletransporting signals. For example, a message may include an analogelectrical signal or digital signal that constitutes binary informationthat may be interpreted as communicating information. Additionally, amessage may comprise any number of pieces of information including bothprivate and/or public information. Messages may be communicatedinternally between devices within a secure organization or externallybetween a device within a secure organization or network to a deviceoutside of a secure organization, area, or communication network.Additionally, whether information contained within a message isconsidered public or private may be dependent on who the secureorganization or area originating the message is, who the message isbeing sent to (e.g., recipient computer or requesting computer), or inany other suitable manner. Additionally, messages may be modified,altered, or otherwise changed to comprise encrypted or anonymizedinformation.

The term “account identifier” may refer to any information that may beused to identify an account. The account identifier can be representedas a series of alphanumeric characters, one or more graphics, a token, abar code, a QR code, or any other information that may be associatedwith an account. For example, the account identifier may be an accountnumber associated with a financial account, or may be a specialidentifier generated randomly or according to a predetermined algorithm,code, or shared secret. The account identifier for a financial accountmay be generated by an issuer associated with the financial account, anddistributed to the payment processing network. In some embodiments, theaccount identifier may be stored in a memory component of a user device.The account identifier may also be embedded in a payment device, such asin a magnetic stripe portion of a payment device in the form of apayment card.

The term “transaction” may refer to a transfer of value between twousers (e.g. individuals or entities). A transaction may involve theexchange of monetary funds, or the exchange of goods or services formonetary funds between two individuals or entities. A typicaltransaction, as contemplated by embodiments of the claimed invention,involves the transfer of funds from a first account associated with afirst payment device to a second account associated with a secondpayment device. In other embodiments, a transaction may involve anindividual or entity purchasing goods or services from a merchant orother entity in exchange for monetary funds. In other embodiments, thetransaction may be a non-financial-related request, such as exchangingof data or information between two entities.

The term “transaction request message” may include a message sent fromone entity to another entity requesting that a transaction beauthorized. In some embodiments, the transaction request message may bean authorization request message from a merchant or acquirer computerrequesting that an issuer authorize a financial transaction. In otherembodiments, the transaction request message may be a request for anon-financial transaction, such as requesting data, coupons, etc. Thetransaction request message may be sent from the computing devicethrough the mobile network to one or more other mobile networks,including a payment processing network mobile network.

The term “transaction response message” may include a message sent fromone entity to another entity responding to a transaction requestmessage. In some embodiments, the transaction response message may be anauthorization response message from an issuer to a merchant or acquirercomputer authorizing or declining a financial transaction. In otherembodiments, the transaction response message may be a response for anon-financial transaction, such as providing data, coupons, etc. Thetransaction response message may be sent from the issuer computerthrough the mobile network to one or more other mobile networks, and toa computing device that made the request.

The term “user” may refer to an individual or entity. The user may be aconsumer or business who is associated with a financial account andwhose financial account can be used to conduct financial transactionsusing a user device associated with the financial account.

The term “server computer” may include a powerful computer or cluster ofcomputers. For example, the server computer can be a large mainframe, aminicomputer cluster, or a group of servers functioning as a unit. Inone example, the server computer may be a database server coupled to aWeb server. The server computer may be coupled to a database and mayinclude any hardware, software, other logic, or combination of thepreceding for servicing the requests from one or more client computers.The server computer may comprise one or more computational apparatusesand may use any of a variety of computing structures, arrangements, andcompilations for servicing the requests from one or more clientcomputers.

The term “payment processing network” may refer to a network thatincludes or operates at least one server computer used for paymentprocessing. In some embodiments, the server computer may be coupled to adatabase and may include any hardware, software, other logic, orcombination of the preceding for servicing the requests from one or moreclient computers. The server computer may comprise one or morecomputational apparatuses and may use any of a variety of computingstructures, arrangements, and compilations for servicing the requestsfrom one or more client computers. In some embodiments, the paymentprocessing network may operate multiple server computers. In suchembodiments, each server computer may be configured to processtransaction for a given region or handles transactions of a specifictype based on transaction data. The server computer may be referred toas a “payment processing server.”

The payment processing network may include data processing subsystems,networks, and operations used to support and deliver authorizationservices, exception file services, and clearing and settlement services.An exemplary payment processing network may include VisaNet™. Networksthat include VisaNet™ are able to process credit card transactions,debit card transactions, and other types of commercial transactions.VisaNet™, in particular, includes an integrated payments system(Integrated Payments system) which processes authorization requests anda Base II system, which performs clearing and settlement services. Thepayment processing network may use any suitable wired or wirelessnetwork, including the Internet.

The payment processing network may process transaction request messagesand determine the appropriate destination (e.g., issuer computer) forthe transaction request messages. The payment processing network mayalso handle and/or facilitate the clearing and settlement oftransactions.

B. Systems

FIG. 1 shows an existing system 100 for transferring data from acomputing device 102 (e.g., mobile device, point of sale device, accessdevice, merchant computer, acquirer computer) communicating with a firstmobile communication network to a payment processing network (PPN)server computer 110. The system 100 includes a computing device 102, afirst mobile network MNO1 104, a second mobile network MNO2 106, aswitch 108, a payment processing network server computer 110, and anissuer computer.

Mobile network MNO1 104, as depicted in FIG. 1, includes a plurality ofbase stations (“BTS”) 104 a and 104 b, each including a PPN conversionmodule 104 a-1 and 104 b-1, respectively. The PPN conversion modules(104 a-1 and 104 b-1) may include hardware, software, and othercommunications infrastructure installed at base stations of mobilenetworks to facilitate the conversion and transmission of data messagesfrom the mobile networks MNO1 104 and MNO2 106 to the PPN servercomputer 110. Each PPN conversion module (104 a-1 and 104 b-1) mayconvert the data messages from a first communication protocol (e.g., SS7protocol) to a second communication protocol (e.g., internet protocol)to communicate with the PPN server computer 110. It should be understoodthat the PPN conversion modules (104 a-1 and 104 b-1) performs theconversion locally within the local mobile network of a computingdevice, and that once a data message has been converted, for example,from SS7 protocol to internet protocol, the data message can no longerbe roamed to a remote location using mobile networks, but is insteadtransmitted using internet protocol network equipment.

Mobile network MNO1 104 may also include a mobile switching center(“MSC1”) 104 c and a gateway mobile switching center (“GMSC1”) 104 d.The base stations 104 a and 104 b may communicate with the MSC1 104 cfor the performance of mobile network functions, including handovers ofcomputing devices between base stations, and transmitting messagesreceived by the base stations 104 a and 104 b. As shown in FIG. 1,mobile network MNO2 106 may have an identical structure and componentsas mobile network MNO1 104. In some embodiments, mobile network MNO1 104and mobile network MNO2 106 may be owned and operated by differentmobile network operators (e.g., telecommunications service providers).

The switch 108 may be a device that is configured to communicativelycouple a plurality of mobile networks. This may allow computing deviceslocated throughout a small region or throughout the world to communicatewith each other. In some embodiments, switch 108 may be a publicswitched telephone network (PSTN) switch, and may be part of a telephonynetwork that aggregates interconnected circuit-switching telephonenetworks. The switch 108 allows mobile and telephone devices to connectto one another and allows data from one mobile network to be sent to asecond mobile network. Each mobile network (e.g., MNO1 104 and MNO2 106)is connected to the switch 108 to facilitate telephone communicationsbetween mobile networks. In some embodiments, the switch 108 utilizesthe Signaling System No. 7 (“SS7”) signaling protocol for the exchangeof control information associated with the establishing and release of atelephone communication between mobile networks. As shown in FIG. 1,mobile network MNO1 104 may communicate with the switch 108 viasignaling channel 2 a, while mobile network MNO2 106 may communicatewith the switch 108 via signaling channel 2 b. Signaling channels 2 aand 2 b may also utilize SS7.

A computing device 102 may be a device that is used to conduct atransaction or to send and receive data messages over a mobile network104 and 106. In some embodiments, the computing device 102 is a merchantcomputer or an acquirer computer. In other embodiments, the computerdevice may be a mobile device configured to communicate over a mobilenetwork. In such embodiments, the computing device 102 is typically asystem for an entity (e.g. a bank) that has a business relationship witha particular merchant or other entity.

The issuer computer 112 is typically a business entity (e.g. a bank)which maintains financial accounts for a user. An acquirer computer istypically a system for an entity (e.g. a bank) that has a businessrelationship with a particular merchant or other entity. Some entitiescan perform both issuer computer 112 and acquirer computer functions.Embodiments of the invention encompass such single entityissuer-acquirers.

In system 100 shown in FIG. 1, the computing device 102 is locatedwithin the circular area surrounding BTS 106 b, representing thegeographic region handled by BTS 106 b. Hence as shown, computing device102 is local to BTS 106 b. For example, when a user conducts atransaction with a merchant associated with the computing device 102, atransaction request message is generated at the computing device 102 andsent to BTS 106 b over the mobile communication network. The PPNconversion module 106 b-1 in BTS 106 b receives the transaction requestmessage and converts the transaction message from SS7 to an internetprotocol (IP). The converted transaction request message in the IPprotocol may then be transmitted to the payment processing networkserver computer 110 along IP network connection 1 d. The paymentprocessing network server computer 110 may then perform traditionaltransaction request message processing. For example, the paymentprocessing network server computer 110 may send the transaction to theissuer computer 112 for authorization or rejection of the transaction.

FIG. 2 shows a system 200 for transferring data from a computing device202 to a payment processing network (PPN) mobile network 210 using amobile communication network according to an embodiment of the presentinvention. The system 200 may be used to facilitate the communicationsof data between a computing device 202 and a payment processing networkserver computer 210 d. The system 200 includes a computing device 202,mobile network MNO1 204, mobile network MNO2 206, a switch 208, a PPNmobile network 210, and an issuer computer 212. For simplicity ofillustration, a certain number of components are shown in FIG. 2. It isunderstood, however, that embodiments of the present invention mayinclude more than one of each component. In addition, some embodimentsof the present invention may include fewer than all of the componentsshown in FIG. 2.

The computing device 202 may include a processor and a computer readablemedium coupled to the processor, the computer readable medium comprisingcode, executable by the processor for performing the functionalitydescribed below. The computing device 202 may be one of a mobile device,point of sale device, access device, merchant computer, acquirercomputer, or any other device that is capable of sending and receivingcommunications through a mobile network. In some embodiments, thecomputing device 202 may be located at a merchant or acquirer location.In some embodiments of the present invention, the computing device 202may include a subscriber identifier issued by the PPN mobile network 210(e.g., a subscriber identifier stored in a SIM card or other securemodule). A SIM card is an integrated circuit that may securely store theinternational mobile subscriber identity (IMSI) and the related key usedto identify and authenticate the computing device 202 as being asubscriber to the PPN mobile network 210. In some embodiments, the SIMcard may be provided to subscribers of the PPN mobile network 210 to beplaced inside the subscribers' computing devices. In other embodiments,the PPN mobile network 210 may provide the computing devices 202 to thesubscriber with the subscriber identifier preloaded into computingdevices or with a SIM card pre-installed. The SIM card issued by the PPNmobile network 210 may facilitate the communication of bothtransaction-related and non-transaction related data between thecomputing device 202 and the payment processing network server computer210 d by identifying the computing device 202 as being subscribed to thePPN mobile network 210.

The computing device 202 may further include a protocol conversionmodule configured to encapsulate a transaction request message in amobile network protocol (e.g., SS7 signaling protocol). The protocolconversion module in the computer device 202 may further be configuredto send the encapsulated transaction request message to the base station206 b for transmission through the mobile network MNO2 206, through theswitch 208, and to the PPN mobile network 210. The protocol conversionmodule in the computer device 202 may also be configured to decapsulatetransaction response messages received from the PPN mobile network 210via the mobile network.

As depicted in FIG. 2, mobile network MNO1 204 may include a pluralityof base stations (“BTS”) 204 a and 204 b, a mobile switching center MSC1204 c and a gateway mobile switching center GMSC1 204 d. Mobile networkMNO2 106 may have an identical structure and components as mobilenetwork MNO1 104. However, each mobile network may include additional orfewer components, including different numbers of base stations based onthe geographic reach of each mobile network. Mobile network MNO1 104 andmobile network MNO2 106 may be owned and operated by different mobilenetworks (e.g., telecommunications service providers). Additionaldetails regarding the components of a mobile network are presented belowand with respect to FIG. 3.

The base stations (204 a, 204 b, 206 a, and 206 b) may be systems thatare responsible for handling communications traffic and signaling to thecorresponding mobile switching center (204 c and 206 c). In embodimentsof the present invention, a typical base station may include equipmentand hardware for transmitting and receiving radio signals, antennas, andequipment for encrypting and decrypting communications. In someembodiments of the present invention, the base stations may communicatewith a corresponding mobile switching center via an in-band data channel(e.g., voice or other data channel) and an out-of-band signaling channel(e.g., control signaling channel such as SS7). In some embodiments, theout-of-band signaling channel may use an SS7 communications protocol tofacilitate the establishment and release of a telephone connectionbetween devices. The in-band channel may be used to carry voice data(e.g., a telephone call) between devices. The base station may becapable of transmitting and processing communications for any mobilecommunication protocol. The circular regions surrounding each of thebase stations (204 a, 204 b, 206 a, and 206 b) are a graphicalrepresentation of the geographic coverage area that each base station isconfigured to send and receive mobile communications to and fromcomputing devices. As shown in FIG. 2, base station 206 b may facilitatecommunications between the computing device 202 and the mobile switchingcenter 206 c.

The mobile switching center (204 c and 206 c) may be a system configuredfor routing data and signals within the mobile network (204 and 206).The mobile switching center (MSC) may be responsible for routing voicecalls, short message service (SMS) messages, and other data through themobile network (204 and 206). The mobile switching center (204 c and 206c) may be configured to set-up and release end-to-end connections andperform handover operations.

The gateway mobile switching center (204 d and 206 d) may be a systemconfigured to determine which mobile switching center the destinationdevice or system is currently located at. Communications from onecomputing device (e.g., mobile phones) to another computing device aretypically routed from a base station to a switch (e.g., a publicswitched telephone network) through the gateway mobile switching center(204 d and 206 d). In some embodiments, the mobile switching center (204c and 206 c) and the gateway mobile switching center (204 d and 206 d)may be a single component within the mobile network performing thefunctions of both the mobile switching center (204 c and 206 c) and thegateway mobile switching center (204 d and 206 d).

The switch 208 may be a device configured to receive and directcommunications data between mobile networks. In some embodiments, theswitch 208 may be a public switched telephone network that is configuredto aggregate interconnected circuit-switching telephone networks. Theswitch 208 allows mobile and telephone devices to connect to oneanother. Each mobile network (e.g., MNO1 204 and MNO2 206 in FIG. 2) isconnected to the switch 208 to facilitate telephone communicationsbetween mobile networks. In some embodiments of the present invention,the switch 208 may utilize a Signaling System No. 7 (“SS7”) signalingprotocol for the exchange of control information associated with therouting, establishing and release of a telephone communication betweenmobile networks. As shown in FIG. 2, mobile network MNO1 204 maycommunicate with the switch 208 via signaling channel 2 a, while mobilenetwork MNO2 206 may communicate with the switch 108 via signalingchannel 2 b. The switch 208 allows mobile network MNO1 204 and MNO2 206to communicate with each other. The switch 208 may also be operablyconnected to the PPN mobile network 210 via signaling channel 1. In FIG.2, the signaling channels (1, 2 a, and 2 b) may include both in-band(e.g., voice/data) and out-of band (e.g., call setup, data transmission)signaling between the PPN mobile network 210, and the mobile networks(204 and 206).

The PPN mobile network 210 may be comprised of at least a base station(BTS) 210 a, a PPN gateway mobile switching center (GMSC) 210 b, a PPNmobile switching center (“PPN MSC”) 210 c, and a payment processingnetwork server computer 210 d. The PPN mobile switching center 210 c mayalso be referred to as a central mobile switching device. In someembodiments of the present invention, the PPN mobile network 210 may beowned and operated by a payment processing network (e.g., Visa®,American Express®, MasterCard®).

The PPN mobile switching center 210 c may include a processor and acomputer readable medium coupled to the processor, the computer readablemedium comprising code, executable by the processor for performing thefunctionality described below. The PPN mobile switching center 210 c inthe PPN mobile network 210 may further include a protocol conversionmodule 210 c-1. The protocol conversion module 210 c-1 may be configuredto receive a data message in a first protocol that is encapsulating adata message in a second protocol. For example, the received datamessage may be an SS7 message (the first protocol) encapsulating a datamessage generated by the computing device 202 in a second protocol(e.g., an internet protocol). In some embodiments of the presentinvention, a stream control transmission protocol (STCP) may be used todecode or decapsulate an IP message from an SS7 signal sent to the PPNmobile switching center 210 c. In such embodiments, the protocolconversion module 210 c-1 may further encapsulate the IP data messageinto an SS7 signal when sending a data message back to the computingdevice 202.

In some embodiments, because the SS7 messages being sent to PPN mobilenetwork are not being used to place actual voice calls but are insteadbeing used to transmit transaction information, certain types of SS7messages or certain portions of SS7 messages that are not required forrouting the SS7 messages can be repurposed to encapsulate data messagescontaining the transaction information. For example, in someembodiments, the transaction information can be encapsulated in theoptional parameter fields of a SS7 ISDN user part (ISUP) message, in theoptional parameter fields of a SS7 signaling connection control part(SCCP) message, and/or in a SS7 transaction capabilities applicationpart (TCAP) message. In some embodiments, the transaction informationmay or may not be encapsulated in a SS7 mobile application part (MAP)message.

The protocol conversion module 210 c-1 may be capable of receiving,converting, and sending transaction messages or any other communicationsbetween entities within a mobile networks system from a central location(e.g., the PPN mobile switching center 210 c) within the PPN mobilenetwork 210. Further, the protocol conversion module 210 c-1 may becapable of distributing and processing transaction data, consumerrequests, notifications, alerts, offers, and any other communicationsover either a mobile telecommunications network or internet protocoltransaction system.

The payment processing network (PPN) server computer 210 d may include aprocessor and a computer readable medium coupled to the processor, thecomputer readable medium comprising code, executable by the processorfor performing the functionality described below. The payment processingnetwork (PPN) server computer 210 d may be configured to processtransaction request and response messages and determine the appropriatedestinations for routing the transaction request and response messages.The payment processing network may also be configured to handle theclearing and settlement of transactions between an issuer and anacquirer. The payment processing network may also be configured togenerate and send messages (e.g., notifications, alerts) to issuers,acquirers, or to the computing device 202.

The issuer computer 212 is typically a business entity (e.g. a bank)which maintains financial accounts for a user. An acquirer computer istypically a system for an entity (e.g. a bank) that has a businessrelationship with a particular merchant or other entity. Some entitiescan perform both issuer computer 212 and acquirer computer functions.Embodiments of the invention encompass such single entityissuer-acquirers.

In the system 200 shown in FIG. 2, the computing device 202 is locatedwithin the circular area surrounding the base station 206 b,representing the geographic region handled by the base station 206 b.When a user engages in a transaction, for example, with a merchantassociated with the computing device 202, or attempts to send a datamessage for performing a transaction, a message (e.g., a transactionrequest message) is generated at the computing device and sent to thebase station 206 b. The base station 206 b may then send the message tothe MSC2 206 c. In some embodiments, the message may be sent on anout-of-band signaling channel (e.g., using an SS7 protocol or othermobile network communication protocol). The message may then be sent tothe switch 208 via the GMSC2 206 d along signaling channel 2 b. Theswitch 208 routes the converted transaction request message to the PPNmobile network 210 where it may be converted by the protocol conversionmodule 210 c-1 to an IP message before being sent to the paymentprocessing network server computer 210 e for processing. Thus, themessage from computing device 202 is received at the PPN mobile network210 via the out-of-band signaling channel, and then subsequentlyconverted into an IP message.

FIG. 3 shows a detailed system diagram for a system configured totransfer data across a mobile network between a computing device 302 anda payment processing network (PPN) mobile network 310 according to anembodiment of the present invention. FIG. 3 shows the devices used fortransferring data from the computing device 302 to the PPN mobilenetwork 310 using mobile network communications systems according to anembodiment of the present invention. The computing device 302 may be asubscriber of the PPN mobile network 310. As depicted in FIG. 3, thecomputing device 302 is roaming or stationed outside of the coveragearea of the PPN mobile network 310.

In embodiments of the present invention, the PPN mobile network 310 maycomprise the hardware components, databases, and facilities describedbelow, such that subscribers to a payment processing network's mobilepayment capabilities may be identified and may communicate acrossmultiple mobile communication networks without the need for third partydata conversion systems or infrastructure investment by the paymentprocessing network 314 within other mobile networks. Accordingly, thepayment processing network 314 may use the protocol conversion module310 i shown in FIG. 3 to communicate with the computing device 302located on the mobile network 306 through the use of SS7 signalingchannels. The ability of the computing device 302 subscribed to the PPNmobile network 310 to communicate and use services from the mobilenetwork 306 may be based on international roaming agreements between thepayment processing network mobile network 310 and the mobile networkoperator of mobile network 306.

The system 300 includes a computing device 302, a mobile network 306, aswitch 308, a payment processing network mobile network 310, an issuercomputer 312, and a payment processing network 314. For simplicity ofillustration, a certain number of components are shown in FIG. 3. It isunderstood, however, that embodiments of the present invention mayinclude more than one of each component. In addition, some embodimentsof the present invention may include fewer than all of the componentsshown in FIG. 3. The description of some components and devices in FIG.3 can be found in the description of FIG. 2 above.

The PPN mobile network 310 may be comprised of at least a PPN basetransceiver station (BTS) 310 a, a PPN base station controller (BSC) 310b, a PPN mobile switching center (MSC) 310 c, a PPN gateway mobileswitching center (GMSC) 310 d, an equipment identity register (EIR) 310e, a visitor location register (VLR) 310 f, a home location register(HLR) 310 g, and an authentication center (AuC) 310 i. Other mobilenetworks may also include components similar or identical to those inthe PPN mobile network 310.

A base station, as described with respect to FIG. 2 may be composed of abase station tower (BTS) (306 a and 310 a) and a base station controller(BSC) (306 b and 310 b). According to some embodiments of the presentinvention, a computing device 302 may send/transmit and receive signalsand data via a base station tower (302 a and 306 a) and a base stationcontroller (302 b and 306 b) between the mobile network 306 and the PPNmobile network 310. In some embodiments of the present invention, theremay be a plurality of base station towers 302 a in communication with asingle base station controller 302 b.

The equipment identity register (EIR) 302 e may be a database storingdevice data for computing devices in the PPN mobile network 310. Theequipment identity register 302 e may keep track of all the black listedcomputing devices (e.g., mobile phones, POS devices, merchant/acquirercomputers) that are banned from accessing the PPN mobile network 310 andservices provided by the PPN mobile network 310. The black listedcomputing device may be identified by the computing device'sinternational mobile station equipment identity (IMEI) that may bestored in the SIM card of the computing device. The data stored in theEIR 302 e may also be used to track stolen computing devices. In someembodiments, the EIR 302 e may be integrated with the home locationregister (HLR) 302 g.

In some embodiments of the present invention, when a computing device302 tries to communicate with a mobile network (for example, PPN MSC310), the IMEI of the computing device 302 may be queried against theEIR database 310 e to determine whether the computing device 302 ispresent on the EIR database 310 e. If the computing device 302 is on theEIR list, the computing device 302 may be prevented from accessing thePPN mobile network 310.

The visitor location register (VLR) 310 f may be a database storing userdata and device data for a mobile network. The visitor location register310 f may be a database of the subscribers (e.g., computing devices)that are presently located within the coverage area of a particularmobile switching center (MSC). For example, the computing device 302 inFIG. 3 is in the coverage area of the mobile network 306 (specificallywithin the coverage area of the base station transceiver 306 a) and thedevice data for the computing device 302 may be stored in a visitorlocation register associated with the mobile network 206 (not shown).The visitor location register 310 f may receive the user data and devicedata from the home location register (HLR) 310 g, which holds permanentdata regarding the mobile network's subscribed computing devices.

In some embodiments of the present invention, the visitor locationregister 310 f may include, but is not limited to, the subscriberidentifier (e.g., an international mobile subscriber identity (IMSI)), aconnection identifier associated with the subscriber identifier (e.g., amobile subscriber integrated services digital network-number (MSISDN)),the mobile network services that the subscriber (e.g., computing device302) is allowed to access, and the home location register address of thecomputing device 302.

In embodiments of the present invention, when the computing device 302moves into the coverage area of the mobile network 306, thecorresponding record is updated in the visitor location register of themobile network 306. Subsequently, the home location register 310 g ofthe PPN mobile network 310 is automatically notified of the change sothat the record in the home location register 310 g for the computingdevice 302 is updated with the roaming location of the computing device302. As the computing devices in the visitor location register 310 f maybe those that are presently in the coverage area of the PPN mobileswitching center 310 c, the data entries change frequently and may bedeleted once a computing device has moved out of the coverage area. Thenotifications and control messages sent between the various mobilenetwork HLRs, VLRs, and other components may be out-of-bandcommunications messages transmitted across an out-of-band signalingchannel (e.g., SS7 communications signaling channel). In someembodiments, the HLRs and VLRs can exchange information using othernetwork protocols (e.g., IP).

The home location register (HLR) 310 g may be a database storing userdata and device data for a mobile network. The data stored by the homelocation register 310 g may include the subscriber identifier (e.g., aninternational mobile subscriber identity (IMSI)) and a connectionidentifier associated with the subscriber identifier (e.g., a mobilestation international subscriber directory number (MSISDN)) of thecomputing device 302 and all other computing devices that are subscribedto the PPN mobile network 310. The subscriber identifier (e.g., IMSI) isused to uniquely identify each Subscriber Identity Module (SIM). TheIMSI may also be used as the primary key for each home location register310 g record. The connection identifier (e.g., MSISDN) may include thetelephone number for each subscribed computing device. The home locationregister 310 g record for each computing device may also include thecurrent location of the computing device 302, which may be obtained fromthe visitor location register of a mobile network 306 in which thecomputing device 302 is roaming in. The home location register 310 grecord for each computing device 302 may be updated when the SIMassociated with the device moves into another area covered by adifferent mobile network 306. The subscriber information that is passedbetween the home location register of the PPN mobile network 310 and thevisitor location register of the mobile network 306 may be passed usingan Update Location Message sent across out-of-band signaling channels(e.g., an SS7 signaling channel) or through an IP network.

The authentication center (AuC) 310 h is a component in a mobile networksystem that may be configured to facilitate the process ofauthenticating each subscriber identity module (SIM) card that attemptsto connect to the PPN mobile network 310. In some embodiments, each SIMcard is assigned an authentication key (K). The authentication key isalso provided to the AuC 310 h. During the authentication process, theauthentication key, a random number, and an algorithm identifier areprovided to the mobile switching center 310 c for generating a firstsecure value using the authentication key and the random number. Therandom number is sent to the SIM, which is used to generate a secondsecure value. The second secure value is sent back to the mobileswitching center 302 c and compared to the first secure value. If thefirst secure value and the second secure value match, the SIM card isauthenticated. Successful authentication of the SIM card (and thus thecorresponding computing device 302), allows the computing device 302 toutilize the services provided by the PPN mobile network 310.

In alternative embodiments of the present invention, the computingdevice 302 may be a Wi-Fi computing device. In such embodiments, in theabsence of a SIM card, the authentication center 310 h may store userlogin data or other user credentials (e.g., email address, e-walletcredentials) in order to authenticate the computing device 302. In suchembodiments, the authentication center 310 h may require additionaldatabases or additional fields to store authentication data for Wi-Ficomputer devices, and/or may require alternative authentication systemsto perform non-SIM card data authentications.

The mobile network 306 may be a second mobile network 306 that isseparate from the PPN mobile network 310 and may be operated by a secondmobile network provider. The mobile network 306 may include a basetransceiver station (BTS) 306 a, a base station controller (BSC) 306 b,a mobile switching center (MSC) 306 c, a gateway mobile switching center(GMSC) 306 d. Although not depicted, the mobile network 306 may havesimilar components to the PPN mobile network 310, including an EIR, VLR,HLR, and AuC.

The payment processing network (PPN) server computer 314 may include aprocessor and a computer readable medium coupled to the processor, thecomputer readable medium comprising code, executable by the processorfor performing the functionality described below. The payment processingnetwork (PPN) server computer 314 may be configured to processtransaction request and response messages and determine the appropriatedestinations for routing the transaction request and response messages.When the transaction is a payment transaction, the payment processingnetwork server computer may be configured to process transaction requestand response messages. The payment processing network 314 may also beconfigured to handle the clearing and settlement of transactions betweenan issuer computer 312 and an acquirer computer 302. The paymentprocessing network 314 may also be configured to generate and sendmessages (e.g., notifications, alerts) to issuer computers 312 or to thecomputing device 202 (e.g., mobile devices, merchant computers, acquirercomputers, etc.). In some embodiments of the present invention, thepayment processing network 314 may include one or more of anauthorization module, a routing module, a clearing and settlementmodule, and a messaging module.

The authorization module may comprise functionality in order to generateand transmit authorization messages to an issuer computer 312 associatedwith a transaction in order to complete the transaction. Accordingly,the authorization module may generate, transmit, or process anyauthorization request messages associated with transactions, theprocessing of e-commerce transactions, or any other functionality inline with typical payment processing functions.

The routing module may be configured to route messages to and from theappropriate destination, such as the issuer computer 312, as part oftransaction processing. The routing module may further handle therouting of clearing and settlement messages or files between thecomputing device 302 and the issuer computer 112 related to the clearingand settlement process.

The clearing and settlement module may comprise all of the clearing andsettlement functionality of the payment processing network 314. Forexample, the clearing and settlement module may perform the clearing andsettlement functions at a predetermined interval or time (e.g., at theend of a business day) for transactions conducted by a merchant. Anexample of the clearing and settlement module is the Base II dataprocessing system, which provides clearing, settlement, and otherinterchange-related services.

The messaging module may send and receive transaction request messagesand transaction response messages, including authorization request andresponse messages, as well as generate and send notification messages,incentive messages, rewards messages, etc.

C. Methods

Methods according to embodiments of the invention can be described withrespect to FIGS. 2-3. FIG. 4 is a flowchart describing a method ofprocessing a transaction using a payment processing network mobilenetwork 310 shown in FIG. 3.

In step 402, a mobile switching center (e.g., PPN mobile switchingcenter 310 c) associated with a first mobile network (e.g., the PPNmobile network 310) operated by a payment processing server 314 receivesa transaction request message from a computing device 302 communicatingwith a second mobile network (e.g., mobile network 306). In someembodiments, the transaction request message may be an authorizationrequest message. In some embodiments, the transaction request messagemay be received by the mobile switching center 310 c via a switch 308(e.g., a public switch telephone network). In embodiments of the presentinvention, the second mobile network may be remote from the first mobilenetwork 310. In such embodiments, the computing device 302 may be localto the second mobile network 306 in that the computing device 302 iscommunicating with the second mobile network 306 via a base transceiverstation 306 a associated with the second mobile network 306. Inembodiments of the present invention, the transaction request message isreceived by the PPN mobile switching center 310 c via a switch 308communicatively coupling the PPN mobile network 310 and the mobilenetwork 306.

For example, the computing device 302 may be a point of sale device at amerchant, where the computing device 302 includes a SIM card issued bythe PPN mobile network 310. The consumer may engage in a transactionwith the merchant by swiping a payment device through a computing device302 in the form of a point of sale (POS) terminal or merchant accessdevice (e.g., ATM), or by passing the payment device within proximity tothe POS terminal. In some embodiments, the POS terminal may extractTrack 2 data (e.g., a primary account number (PAN), expiration date,CVV, etc.) from a magnetic stripe portion or contactless communication(e.g., near-field communication (NFC)) element of a payment device. Insome embodiments, a token or other account identifier substitute may begenerated or stored in the payment device instead of the primary accountnumber. The POS terminal may use the Track 2 data to generate atransaction request message (e.g., an authorization request message)including the transaction details (e.g., transaction amount, merchantidentifier, payment data, CVV, encrypted PIN), to send to an issuer forapproval or rejection of the transaction. In some embodiments, thetransaction request message may be an ISO 8583 message used forfinancial transaction.

When a consumer engages in a transaction with the merchant using thecomputing device 302, the computing device 302 may generate and send thetransaction request message to the base transceiver station 306 aassociated with the mobile network 306. In embodiments of the presentinvention, the computing device 302 may send the transaction requestmessage to the base transceiver station 306 a that the computing device302 is in range of or communicating with. A base transceiver controller306 b associated with the base transceiver station 306 a may send thetransaction request message to the mobile network mobile switchingcenter 306 c using an SS7 signaling protocol. In such embodiments, thetransaction request message may be in an internet protocol andencapsulated within an SS7 signal.

The transaction request message may include a recipient identifieridentifying the destination of the transaction request message oridentifying the mobile network that the computing device 302 issubscribed to (e.g., the PPN mobile network 310). The mobile networkmobile switching center 306 c may then query a visitor location registerassociated with the mobile network 306 to determine the PPN mobilenetwork 310. After determining the PPN mobile network 310, the mobileswitching center 306 c of the second mobile network 306 may send thetransaction request message to the switch 308 via a gateway mobileswitching center 306 d. In some embodiments, an international roamingagreement may be established between the PPN mobile network 310 and themobile network 306 before the mobile network 306 will send thetransaction request message to the PPN mobile network 310. The switch308 may then send the transaction request message to the PPN mobileswitching center 302 c in the PPN mobile network mobile 310 via the PPNgateway mobile switching center 310 d.

In step 404, the transaction request message is converted from a firstprotocol to a second protocol by a protocol conversion module 310 i. Insome embodiments of the present invention, the first protocol may be anSS7 signal protocol and the second protocol may be an internet protocol.Once the PPN mobile switching center 310 c receives the transactionrequest message, the transaction request message may be sent to theprotocol conversion module 310 i. In embodiments of the presentinvention, the protocol conversion module 310 i may be a module withinthe PPN mobile switching center 310 c. In other embodiments, theprotocol conversion module 310 i may be separate from the PPN mobileswitching center 310 c but within the PPN mobile network 310.

In embodiments of the present invention, converting the transactionrequest message may include using a stream control transmission protocolto decapsulate and/or decode the transaction request message that wasencapsulated within an SS7 signaling message.

In step 406, the converted transaction request message is sent to thepayment processing network server computer 314. Once the paymentprocessing network server 314 receives the converted transaction requestmessage, the payment processing network server computer 314 may processthe transaction contained in the converted transaction request message.This process may include determining an appropriate issuer computer 312associated with the transaction, and receiving and processingauthorization messages for the transaction.

The processing steps performed by the payment processing network servercomputer may be the same as traditional authorization processes that thepayment processing network server computer is configured to process.Further, the payment processing network server computer 314 may beconfigured to process transaction request messages in IP.

In step 408, a mobile switching center 310 c receives a transactionresponse message from the payment processing server 312. The transactionresponse message may include a response to the transaction request sentfrom the computing device 302. In other embodiments, the transactionresponse message may include one or more of a notification message, acoupon, a receipt, and/or a reward, etc. In some embodiments thetransaction response message may be sent by the payment processingserver 312 in an internet protocol. In embodiments of the presentinvention, the transaction response message may be sent to the PPNmobile switching center 310 c in the PPN mobile network 310 using the IPprotocol.

In step 410, the transaction response message is converted from thesecond protocol (e.g., IP protocol) to the first protocol (e.g., SS7signaling protocol). The transaction response message may be converted(e.g., encapsulated into an SS7 signaling protocol) by the protocolconversion module 310 i prior to being sent back to the computing device302 over the mobile communication network infrastructure. In someembodiments of the present invention, the transaction response messagefrom the payment processing network 110 may be in an internet protocol.In other embodiments, the transaction response message may be in adifferent network protocol. In such embodiments, the protocol conversionmodule 310 i may encapsulate the transaction response message into anSS7 message for transmission to through the mobile networks system 300.

In step 412, the converted transaction response message is sent to thecomputing device 302 via the switch 308. In embodiments of the presentinvention, the PPN mobile switching center 310 c may determine thelocation of computing device 302 as the computing device 302 iscurrently on a different mobile network (e.g., the computing device 302is roaming on mobile network 306). In order to locate the mobileswitching center 306 c of the mobile network 306 that the computingdevice 302 is on, the PPN mobile switching center 310 c may query thehome location register 310 g with the MSISDN number of the computingdevice 302. Typically, when a computing device subscribed to a mobilenetwork is roaming, the visitor location register of the mobile networkthat the computing device is currently roaming on will send a locationupdate message to the home location register of the home mobile networkof the computing device. Thus, in embodiments of the present invention,when the computing device 302 entered the range of the base transceiverstation 306 a of the the mobile network 306, the visitor locationregister of the mobile network 306 would generate and send a locationupdate message to the home location register 310 g of the PPN mobilenetwork 310. This allows the PPN mobile network 310 to store updateddata on the location of the computing device 302 (and all othercomputing devices subscribed to the PPN mobile network 310) in the homelocation register 310 g.

The home location register 310 g may send to the visitor locationregister of the mobile network 306 a provided roaming number (PRN)message to obtain the mobile station roaming number (MSRN) of thecomputing device 302. The home location register 310 g will then be ableto route the call to the correct mobile switching center 306 c. The PRNmessage may be sent using a mobile application part (MAP) protocol,which is an SS7 protocol that provides an application layer for thevarious nodes and components in mobile networks to communicate with eachother in order to provide services to computing device (e.g., mobiledevice) users.

Using the international mobile subscriber identity (IMSI) contained inthe PRN message, the visitor location register in the mobile network 306assigns a temporary number (e.g., the mobile station roaming number(MSRN)) to the computing device 302. The MSRN number is sent back to thehome location register 310 g in a RIA (Routing InformationAcknowledgement) message. Using the MSRN number, the PPN gateway mobileswitching center 310 d may route the transaction response message to thecomputing device 302 via the switch 308.

Accordingly, embodiments of the invention allow a payment processingnetwork to send and receive communications generated in a knownprocessable protocol by the payment processing network server computeracross mobile network communication infrastructure by encapsulating themessages into a mobile network signaling protocol. In this manner,transaction data originating from around the world can be passed to thepayment processing network at a central location using just mobileand/or telephony networks by utilizing the roaming capabilities of suchnetworks without requiring IP network connectivity between a local basestation and the payment processing network.

II. Location-Aware Communications System

Some embodiments of the integrated communications network may implementa location-aware network communications system that may allow a paymentprocessor to obtain additional information about a consumer using alocation-aware header of a network communication. The information passedin the location-aware header may allow the payment processor the abilityto provide more effective authentication of a consumer during atransaction and provide additional fraud analysis, consumer advertisingtargeting, and any other applications relevant to a payment process. Forexample, a location-aware network header may include a merchantidentifier (e.g., a unique identifier associated with a merchant,service provider, government entity, or any other registered party), alocation identifier (e.g., a particular merchant's store location, alocation within a merchant's store, etc.), a mobile device identifier(e.g., a hardware identifier for the mobile device, a phone number, adevice manufacturer serial number, etc.), a consumer identifier (e.g.,mobile wallet identifier, payment account user name, a phone number,etc.), transaction type indicator (e.g., tracking, payment transaction,etc.), or any combination thereof in order to obtain additionalinformation about the consumer, a transaction, a merchant, etc. in orderto better authenticate, predict consumer behavior, and securetransaction communications.

Furthermore, the location-aware header may be integrated with existingpayment systems by incorporating the location-aware information into anetwork communication header instead of in a transaction payload. Forexample, the location-aware header may be transmitted in the networkprotocol header along with an existing payment message (e.g., ISO 8583standard payment authorization request message) to a payment processorthat may parse the information in the location-aware header messagebefore processing the existing payment message using existingtransaction processing systems. The payment processor may then use theadditional information provided in the location-aware header to furtherauthentication, validate, and complete the transaction. Accordingly,embodiments may be incorporated into existing payment systems at thenetwork communication level without requiring different paymentstandards and authorization systems. The location-aware header may alsobe used to provide additional services, including incentive or rewardsissuance, and notification or alert messaging services.

Furthermore, the location-aware infrastructure provides a benefit byallowing a merchant to target-market to individual consumers. Using thelocation terminals, the merchant may be able to locate the consumer to aparticular type of product or area of the merchant store containing aparticular type of product. This data can be sent to the internetcontroller in the payment processing network to generate anadvertisement, coupon, deal, etc. that is directly relevant to theconsumer's shopping experience. In embodiments where the data from thelocation terminals is regularly sent through the location-aware system,the most relevant offers and promotions may be generated. This savesresources that may be expended sending all offers or promotions to allconsumers.

A. Definitions

Prior to discussing embodiments of the invention, descriptions of someterms may be helpful in understanding embodiments of the invention.

The term “network protocol packet” may refer to a formatted unit of datacarried by a network. Network protocol packets typically include anetwork protocol header (e.g., control) portion and a data (e.g.payload) portion. The network protocol header may include control datathat provides routing, security, and error detection information thenetwork typically requires to deliver the information in the dataportion. For example, the network protocol header may include source anddestination network addresses, error detection codes, and sequencinginformation. An example of a network protocol packet may be a TCP/IPpacket.

The term “location-aware header” may refer to a portion of the networkprotocol header. The location-aware header may store the location-awaredata retrieved by location terminals and POS terminals. In embodimentsof the present invention, the location-aware header may be embeddedwithin the traditional network header by repurposing existing fields ofthe tradition network header, or be prepended, appended, or insertedinto the traditional network header. The location-aware header mayinclude fields for location-aware data.

The term “transaction payload” may refer to a data portion of a networkprotocol packet. In some embodiments of the present invention, thetransaction payload may include transaction data for a financialtransaction (e.g., payment data, transaction total, consumer data). Thetransaction data in the transaction payload may be used for processingthe financial transaction. The transaction data may be in any suitableformat and may include any suitable information depending on thepurposes of the transaction payload. For example, the transactionpayload may include data related to a non-financial transaction,including alert data, incentive data, product data, etc.

The term “location-aware data” may refer to data accessed by merchantdevices. The location-aware data may include mobile device data (e.g.,mobile device identifier), merchant data (e.g., a merchant identifier),consumer data (e.g., a consumer identifier), location data (e.g., alocation identifier), and transaction type data. The location-aware datamay be retrieved from a mobile device associated with a user, from a POSterminal used to conduct a transaction with the mobile device, or fromany other suitable sources associated with a transaction.

The merchant identifier may be a previously assigned identificationnumber for a merchant. In some embodiments, the merchant identifier maybe a numeric or alphanumeric value. The location identifier may be anidentifier corresponding to a physical address or some other geographiclocation. In one embodiment, the location identifier may correspond toan address of the merchant location, which may be stored in a databaseassociated with the payment processing network. The device identifiermay correspond to an identifier of the mobile device. In one embodiment,the device identifier may correspond to data stored on a subscriberidentity module (SIM) of the mobile device. The consumer identifier maycorrespond to an identifier of the consumer associated with the mobiledevice. In one embodiment, the consumer identifier may be a digitalwallet number, an email address, a phone number, or other consumer data.

The term “in proximity to” may refer to the location of devices relativeto each other. In some embodiments of the present invention, thelocation terminals at a merchant location may have a coverage areawithin which the location terminal can retrieve data from mobiledevices. When a mobile device is in the coverage area of the locationterminal, the mobile device may be considered in proximity to thelocation terminal.

The term “consumer-targeted message” may refer to a type of message sentto a consumer. In embodiments of the present invention, aconsumer-targeted message may include an alert, notification, coupon,advertisement, offer, or rewards associated with a merchant. Inembodiments of the invention, incentives may be targeted andlocation-based. For example, based on location data and merchant data inthe location-aware header, the internet controller may generate anincentive for a specific merchant or a specific product based on themerchant location or a specific location of the mobile device within themerchant location. The consumer-targeted message may be sent to theconsumer through a mobile network and displayed on the consumer's mobiledevice or on a merchant point of sale device.

The term “authorization process” may refer to process conducted as partof transaction processing. Typically, an authorization process involvesa payment processing network and an issuer of a payment account orpayment device. The authorization process may involve the generation andsending of authorization request messages to an issuer to authorize afinancial transaction involving a consumer account issued by the issuer,and an authorization response message from the issuer indicating anauthorization or rejection of the transaction.

The term “validating the transaction” may refer to process conductedusing location-aware data. The process of validating the transaction mayinclude comparing data stored in the consumer profile with thelocation-aware data from the location-aware header portion. Thetransaction may be validated when the data stored in the consumerprofile matches the location-aware data received in the location-awareheader portion.

In embodiments of the present invention, when a transaction associatedwith transaction data is authorized by an issuer, the internetcontroller in the payment processing network may conduct an additionalvalidation or verification step. This additional validation may use thelocation-aware data, which includes data not typically transmitted aspart of transaction data for the transaction. For example, the internetcontroller may evaluate a consumer table comprising entries forconsumers based on past transaction history. The consumer table mayinclude a device identifier and a consumer identifier associated withthe device identifier. If the location-aware data includes a deviceidentifier and/or a consumer identifier that do not match the data inthe consumer table, the internet controller may decline to validate thetransaction.

The term “location terminal” may refer to a merchant communicationsapparatus. The location terminal may be a sensing apparatus configuredto detect the presence of the mobile device at or near a merchantlocation. In some embodiments, a single merchant or location have aplurality of location terminals. In some embodiments, the locationterminal may be a standalone device located at a merchant. In otherembodiments, the location terminal may be contained within (orintegrated with) a POS terminal at the merchant. The location terminalmay further be configured to collect information (e.g., consumer data,payment data, device data) associated with mobile device. In someembodiments, the mobile device may include an application configured tosend the consumer data and device data, stored in the memory or themobile device, to the location terminal. In some embodiments of thepresent invention, consumer presence may be detected when a consumer isat or near the location terminal, and the credentials associated withthe consumer (e.g., a payment processing network SIM card) may becollected by intercepting the mobile network communication messagesfrequently being sent from mobile devices. The retrieved data may beplaced (or stored) in a location-aware header portion of a networkprotocol header of a network protocol packet. In some embodiments, theinformation collected by the location terminal may be used for multiplepurposes, such as, enhanced risk analysis, fraud detection,authentication, advertisements, incentives, payment processing, etc.Although discussed in terms of merchant use, the location terminal isnot limited only to applications at merchants and may be implemented byany entity, as one of ordinary skill in the art would recognize.

The term “location proxy device” may refer to a merchant communicationsapparatus. The location proxy device may be configured as a merchantproxy for securely providing the information collected by the locationterminal to an internet controller of the payment processing network.The data may be provided in a network packet via any suitablecommunications network (e.g., the Internet). The location proxy may beconfigured to receive a network protocol packet from one or morelocation terminals and store transaction data generated by a point ofsale device into a transaction payload of a network protocol packet. Thelocation proxy may provide secured and certified communications betweendifferent network communication devices. In some embodiments, merchantdata, location data, device data, and consumer data may also betransmitted to the internet controller via a network packet. Thefunctions of the location proxy may be implemented in hardware or as aplug-in software module.

The term “point of sale device” may refer to a device that can be usedto initiate a transaction. In some embodiments, a point of sale devicecan interact with a portable consumer device (e.g., a payment card orother payment device) during a transaction. According to embodiments ofthe invention, the point of sale device can be in any suitable form.Examples of point of sale devices may include merchant access devices,cellular phones, PDAs, personal computers (PCs), tablet PCs, handheldspecialized readers, set-top boxes, electronic cash registers, automatedteller machines (ATMs), virtual cash registers, kiosks, securitysystems, access systems, and the like. Any suitable point of saledevices may be used including card or mobile device readers. The card ormobile device readers may include any suitable contact or contactlessmode of operation. For example, exemplary readers can include RF (radiofrequency) antennas, magnetic stripe readers, etc. to interact withportable consumer devices.

B. Systems

FIG. 5 shows a transaction processing system 500 with location-awareinfrastructure according to some embodiments of the present invention.The system 500 may be used to facilitate the communications of databetween a mobile device 502 and a payment processing network 514. Thesystem 500 includes traditional transaction-related entities including amerchant 504, an acquirer 506, an issuer 512, and the payment processingnetwork 514 (which may include one or more payment processing networkserver computers 508 a and 508 b serving a single payment processingnetwork 514). The system 500 also includes a mobile device 502, whichmay include consumer account data for a consumer account associated withthe issuer 512. The location-aware infrastructure includes the locationterminal 516, the location proxy 518, and the internet controller 520.For simplicity of illustration, a certain number of components are shownis shown in FIG. 5. It is understood, however, that embodiments of thepresent invention may include more than one of each component. Inaddition, some embodiments of the present invention may include fewerthan all of the components shown in FIG. 5.

The mobile device 502 may be in any suitable form. For example, suitablemobile devices 502 can be hand-held and compact so that they can fitinto a consumer's pocket (e.g., pocket-sized). The mobile device 502 caninclude a processor, and memory, input devices, and output devices,operatively coupled to the processor. Specific examples of portableconsumer devices include cellular or wireless phones, personal digitalassistants (PDAs), pagers, portable computers, smart cards, and thelike.

In a typical transaction, a consumer associated with the mobile device502 may purchase a good or service at the merchant 504 using the mobiledevice 502. For example, the consumer may pass the mobile device 502near a contactless reader in a POS terminal at the merchant 504. Inother embodiments, the consumer associated with the mobile device 502may be moving through a merchant location and data may be retrieved fromthe mobile device 502 by one or more locational terminals 516.

An issuer 512 is typically a business entity (e.g., a bank) which issuesand maintains consumer accounts for a consumer. The issuer may issuepayment devices for the consumer account including credit cards, debitcards, etc., and/or may provide consumer accounts stored and accessiblevia the mobile device 502 of the consumer. An acquirer 506 is typicallya business entity (e.g., a commercial bank) that has a businessrelationship with a particular merchant or other entity and that may beinvolved in the process of transaction. The acquirer 506 may issue andmanage accounts for merchants and exchange funds with the issuer 512 onbehalf of the merchant. Some entities can perform both issuer andacquirer functions. Embodiments of the present invention encompass suchsingle entity issuer-acquirers. The payment processing network 514 mayprovide transaction authorization and clearing and settlement servicesbetween the acquirer 506 and the issuer 512.

The location terminal 516 may include a processor and a computerreadable medium coupled to the processor, the computer readable mediumcomprising code, executable by the processor for performing thefunctionality described below. The location terminal 516 may be asensing apparatus configured to detect the presence of the mobile device502 at or near a merchant location. In some embodiments, the locationterminal 516 may be a standalone device located at a merchant 504. Inother embodiments, the location terminal 516 may contained within a POSterminal at the merchant 504. The location terminal 516 may beconfigured to collect information (e.g., consumer data, payment data,device data) associated with mobile device 502. In some embodiments, themobile device 502 may include an application configured to send theconsumer data, payment data, and device data, stored in the memory orthe mobile device 502, to the location terminal 516. In some embodimentsof the present invention, consumer presence may be detected when aconsumer is at or near the location terminal 516, and the credentialsassociated with the consumer (e.g., a payment processing network SIMcard) may be collected. In some embodiments, the information collectedby the location terminal 516 may be used for multiple purposes, such as,enhanced risk analysis, fraud detection, authentication, advertisements,incentives, payment processing, etc. Although discussed in terms ofmerchant use, the location terminal 516 is not limited only toapplications at merchants and may be implemented by any entity, as oneof ordinary skill in the art would recognize.

The location proxy 518 may include a processor and a computer readablemedium coupled to the processor, the computer readable medium comprisingcode, executable by the processor for performing the functionalitydescribed below. The location proxy 518 may be a merchant communicationsapparatus configured as a merchant proxy for securely providing theinformation collected by the location terminal 516 to an internetcontroller 520 of the payment processing network 514. The data may beprovided in a network packet, as described in further detail in FIG. 9below, via any suitable communications network (e.g., the Internet 524).The location proxy 518 may provide secured and certified communicationsbetween different modules. In some embodiments, merchant data, devicedata, and consumer data may also be transmitted to the internetcontroller 520 via the network packet. The functions of the locationproxy 518 may be implemented in hardware or as a plug-in softwaremodule.

Communications between the location proxy 518 and the internetcontroller 520 may be conducted over a communications network (e.g., theInternet 524). The communications network may include a wirelessconnection, hardwired open network, or closed hardwired network.

The internet controller 520 may include a processor and a computerreadable medium coupled to the processor, the computer readable mediumcomprising code, executable by the processor for performing thefunctionality described below. The internet controller 520 may beconfigured as a controller that communicates with various locationproxies 518 to aggregate consumer and/or transaction information overthe Internet 524 or any other suitable communications network or mediumon behalf of a payment processing network 514. In some embodiments, theinternet controller 520 may provide additional services in transactionprocessing including parsing a location-aware header from a networkprotocol packet, validating transactions, and performing additionalanalyses using the data included in the location-aware header. In someembodiments, the internet controller 520 is a module within the paymentprocessing network 514. In other embodiments, the internet controller520 is a separate entity from the payment processing network 514 andconfigured to aggregate and send data to the payment processing network514.

In some embodiments, communications between the payment processingnetwork 514 and the mobile device 502 may be conducted through a networksuch as the Internet. In other embodiments of the present invention, thecommunications between the payment processing network 514 and the mobiledevice 502 may be conducted through a PPN mobile network 510 via aprotocol conversion module 522. The protocol conversion module may beimplemented using the systems described above with respect to FIGS. 2-4.In such embodiments, communications may be sent using mobile networkprotocols (e.g., SS7 communication protocol).

FIG. 6 shows a detailed system diagram 600 for a system withlocation-aware infrastructure according to an embodiment of the presentinvention. The system 600 illustrates how each merchant location mayaggregate the data specific to its location via location terminals (616a and 616 b) and location proxies (618 a and 618 b), and transmit thedata over the Internet to a single internet controller 620 associatedwith a payment processing network 614. Each merchant location in FIG. 6may be for a different merchant location for the same merchant, or eachmerchant location may be a different merchant location representingdifferent merchants. For example, the merchant may a plurality oflocations and either one location proxy module 618 a aggregating thedata for the plurality of location, or each of the plurality oflocations may include a location proxy module 618 a.

The internet controller 620 may analyze the data and informationreceived from each location proxy 618 a and determine targeted offersfor each consumer associated with each mobile device (602 a and 602 b).For example, the internet controller 620 may generate a coupon (e.g.,20% off total purchase) for the consumer associated with the mobiledevice (602 a and 602 b) that can be used at a merchant at the merchantlocation. In some embodiments, the coupon offer may be generated basedon the consumer's profile (e.g., purchase history at that merchantlocation). For example, the consumer profile may be stored in a database620 b accessible by the internet controller 620. The database 620 b mayinclude the consumer tables described in further detail below inreference to FIG. 10. In another example, the internet controller 620may generate an advertisement for a sale occurring at the merchantlocation that may be transmitted to the mobile device (602 a and 602 b).In yet another example, the internet controller 620 may transmit a listof businesses (e.g., food vendors, banks, movie theaters, shoppingmalls) in proximity to the merchant location to the mobile device (602 aand 602 b).

In embodiments of the present invention, the internet controller 620 maytransmit a data message back to the mobile device 602 a via acommunications network. The data message may include a targeted offer(e.g., coupon, advertisement) for the consumer associated with themobile device 602 a. The data message may be sent to the mobile device602 a through the PPN mobile switching center 610 associated with thepayment processing network 614. In such embodiments, the data messagemay be sent from the PPN server computer 608, through a protocolconversion module 622, and across a PPN mobile network as previouslydescribed with respect to FIG. 2-4. In alternative embodiments, the datamessage may be sent through a third party mobile network. Additionally,in some embodiments, the internet controller 620 may send the datamessage through an internet protocol to the location proxy 618 a toprovide the coupon to the consumer through the location terminal 616 a(e.g., merchant POS terminal or access device).

In some embodiments, when the mobile device 602 a conducts a financialtransaction with the merchant, transaction data may be sent to theinternet controller 620. The payment processing network 614 may also beassociated with a payment gateway of issuers, acquirers and processors612 that performs steps for authorizing a transaction associated withthe transaction data (e.g., authorizing the transaction associated withan authorization request message). In such embodiments, an authorizationresponse message is transmitted by the PPN mobile switching center 610to the mobile device 602 a associated with the consumer. The paymentgateway of issuers, acquirers and processors 612 may also be configuredto store and provide data for consumer-targeted messages includingalerts, notifications, coupons, advertisements, and rewards data. Thedata for the consumer-targeted messages may be stored in databasesaccessible through the payment gateway of issuers, acquirers andprocessors 612.

The internet controller 620 may further include an authentication module620 a and a database 620 b. In embodiments of the present invention, theauthentication module 620 a may be configured to authenticate the mobiledevice (602 a and 602 b). For example, if the mobile device 602 a is inproximity to location terminal 616 a, the location terminal 616 a mayretrieve data from the secure module (e.g., SIM card) of the mobiledevice 602 a or from a software application operating on the mobiledevice providing information from other memory/storage on the mobiledevice. The location terminal may pass the received data in alocation-aware header portion of a network protocol packet 900 (as shownin FIG. 9) to the location proxy module 618 a. The location proxy modulemay send or forward the network protocol packet 900 including thelocation-aware header portion through a communications network (e.g.,the Internet 624) to the internet controller 620.

In some embodiments, the authentication module may authenticate asubscriber identifier and/or device identifier received in the devicedata field 902 b-3 in a location-aware header portion of a networkprotocol packet 900 using stored authentication values associated withthe device and/or consumer operating the device. In some embodiments,the authentication module 620 b may use a consumer identifier (e.g.,email address, e-wallet account data, user login) received in a consumerdata field 902 b-4 in a location-aware header portion of a networkprotocol packet 900 to authenticate the device and/or consumer. If themobile device is authenticated, the processes and functionalitydescribed herein may be completed. If the device or consumer is notauthenticated, the functionality and processes may be stopped.

FIG. 7 shows a block diagram 700 illustrating the multiple communicationmodes that a mobile device is configured to use in an exemplarylocation-aware transaction processing system according to an embodimentof the invention. A mobile device 702 may be capable of operating as adual mode handset (e.g., the mobile device 702 may be capable sendingand receiving data and information via a mobile network and via Wi-Fi.FIG. 7 illustrates that, in some embodiments of the present invention,the location terminals (716 a and 716 b) may be configured to supportboth licensed spectra (e.g., mobile network) and un-licensed spectra(e.g., Wi-Fi, Bluetooth®, Zigbee®, Dash7®, etc.) for a mobile device702. The location terminals (716 a and 716 b) may access data stored onthe mobile device 702 and transmit the data through the location proxy(718 a and 718 b) to an internet controller 720 in the paymentprocessing network 715.

Devices using licensed spectrum may also be referred to as being on acentrally-controlled system. For example, a mobile device 702 operatingon a mobile network is subscribed to a mobile network in order to accessservices. In embodiments of the present invention, when the mobiledevice 702 is accessed by the licensed spectrum location terminal 716 a,the mobile identifier retrieved from the mobile device 702 may be datafrom a SIM card. Data in the SIM card may be sent to the internetcontroller 620, along with other device, merchant, consumer, andlocation data, and used to authenticate the mobile device 702. Forexample, an IMSI associated with the mobile device 702 may beauthenticated by the authentication module 620 a (as shown in FIG. 6).

Devices using unlicensed spectrum may also be referred to as being on adistributed network. Unlicensed spectrum is open for shared use by anunlimited number of users, and is typically used by Wi-Fi or Bluetooth®devices. In embodiments of the present invention, when the mobile device702 is accessed by the unlicensed spectrum location terminal 716 b, themobile identifier retrieved from the mobile device 702 may be a consumercredential or login name.

The computing device 702 may comprise a specialized SIM card or otherspecialized memory that allows the computing device 702 to be identifiedand tied to an account, mobile wallet, or service provided by a paymentprocessing network 708. The computing device 702 may comprise a chip(e.g., a SIM card or other secure module) that includes paymentprocessing network identifier that may be read by the network equipment,bundled into a communication data message, and transmitted to thepayment processing network 714. The payment processing networkidentifier may also allow the computing device 702 and the paymentprocessing network 714 to communicate over an out-of-band signalingchannel through the use of SS7 signaling protocols using embodimentsdescribed above in reference to FIGS. 2-4.

FIG. 8 shows a block diagram illustrating the interaction of multiplelocation-aware infrastructure devices and mobile devices in an exemplarylocation-aware transaction processing system according to an embodimentof the invention. FIG. 8 illustrates the collection of location data andtransaction data at a merchant 804 using a plurality of locationterminals (816 a and 816 b), a POS terminal 806, and a location proxy818. Each location terminal (816 a and 816 b) may have a specificcoverage area within a merchant location, as depicted by the ellipticalshaped regions surrounding each location terminal (816 a and 816 b).Mobile devices located within the elliptical shaped regions may beaccessed by the corresponding location terminal. For example, mobiledevice 1 802 a is within the range of (or in proximity to) locationterminal 816 a, while mobile device 2 802 b is within the range of (orin proximity to) location terminal 816 b.

In some embodiments of the present invention, the location terminals(816 a and 816 b) may collect or be pre-configured with merchant data(e.g., merchant identifier, location identifier). The location terminals(816 a and 816 b) may also collect device data and consumer data fromthe mobile devices (802 a and 802 b) (e.g., device identifier, consumeridentifier). The data retrieved by the location terminals (816 a and 816b) may then be sent to the location proxy 818 in a network header to becombined into a network packet. In some embodiments, a merchant 804 mayhave a plurality of location terminals (816 a and 816 b) within themerchant location and a location proxy 818 that collects the data fromthe plurality of location terminals (816 a and 816 b).

In the example in FIG. 8, a transaction may be conducted between mobiledevice 1 802 using the POS terminal 806 at the merchant 804. The POSterminal 806 may retrieve additional information from mobile device 1802, including but not limited to, hardware data from the mobile device1 802, and transaction data including an issuer identifier and otherpayment device data (e.g., payment account number). The POS terminal 806may send the retrieved data and a transaction type indicator with thetransaction data to the location proxy 818. The data may be sent in anetwork packet 900 formatted as shown in FIG. 9. In embodiments of thepresent invention, the location proxy 818 may associate the data formobile device 1 802 retrieved by the location terminal 806 a with thedata for mobile device 1 802 and the transaction data retrieved sent bythe POS terminal 806. The data from the location terminal 816 a and thedata from the POS terminal 806 may be associated based on a deviceidentifier or consumer identifier common to the data retrieved from thelocation terminal 816 a and the POS terminal 806.

The data may then be packaged into a location-aware header and sent in anetwork protocol packet to the internet controller 820 located at thepayment processing network 814. As noted previously, in someembodiments, the internet controller 820 may be a separate entity fromthe payment processing network 820.

FIG. 9 shows a diagram of a network protocol packet 900 according to anembodiment of the invention. The network protocol packet 900 may includea network protocol header (e.g., control) 902 and a transaction payload(e.g., data) 904. In embodiments of the present inventions, the networkprotocol header 902 may include a traditional network header 902 a and alocation-aware header 902 b. The traditional network header 902 a mayinclude, for example, source and destination addresses (MAC and/orinternet protocol addresses) and similar data used for routing thenetwork protocol packet 900. According to the embodiments as shown, thelocation-aware header 902 b is appended to the traditional networkheader 902 a. In some embodiments, the location-aware header 902 b canbe prepended to the traditional network header 902 a, or be inserted inbetween fields of the traditional network header 902 a (e.g., in betweensource and destination addresses). In some embodiments, an existingfield or fields of the traditional network header 902 a can berepurposed for the location-aware header 902 b. For example, the optionsfield of an IP packet header can be used for the location-aware header902 b.

According to some embodiments, appending the location-aware header 902 bto the traditional network header 902 a, or repurposing an existingfield or fields of the traditional network header 902 a may allow thenetwork protocol packet 900 to be used with existing network equipment.Existing network equipment that may not necessarily have location-awareheader functionalities can still parse the beginning portions of thenetwork protocol packet 900 to perform networking functions (e.g., toobtain source and destination addresses to route the packet). Inembodiments in which the location-aware header 902 b is prepended orinserted in the traditional network header 902 a, the network equipmentreceiving the network protocol packet 900 can be updated to recognizethe modified header format.

In embodiments of the present invention, the location-aware header 902 bmay include data retrieved by the location terminals (816 a and 816 b)and the POS terminal 806, as described in FIG. 8. The retrieved data mayinclude one or more of mobile device data, consumer data, merchant data,location data, and transaction type data. In some embodiments, thenetwork protocol packet may be an IP/TCP protocol packet. Merchant dataincluding a merchant identifier and/or a merchant location may be storedin a merchant data portion 902 b-1 of the location-aware header 902 b.Location data including a location identifier may be stored in alocation data portion 902 b-2 of the location-aware header 902 b. Devicedata including a hardware identifier (e.g., MAC address) may be storedin a device data portion 902 b-3 of the location-aware header 902 b.Consumer data including a consumer identifier (e.g., e-wallet account,email address) may be stored in a consumer data portion 902 b-4 of thelocation-aware header 902 b. Transaction type data indicating whetherthe transaction is a non-financial transaction (e.g., coupon request oraccount information request) or a financial transaction (e.g., purchasetransaction) may be stored in a transaction type portion 902 b-5 of thelocation-aware header 902 b. The location-aware header 902 b may furtherinclude a reserved field 902 b-6 for additional data that may berelevant to verifying or validating a transaction, targeting a consumer,or any other purposes of embodiments of the present invention. Otherembodiments of the present invention may include all of the fieldsdescribed above, fewer fields, or additional fields, as one of ordinaryskill in the art would recognize.

The transaction payload portion 904 of the network protocol packet 900may contain the transaction data for a transaction conducted using themobile device 802 a that is sent from the POS terminal 806 as part ofthe authorization process for the transaction. In some embodiments ofthe present invention, the transaction data in the transaction payloadportion 904 may be in an ISO 8583 message. ISO 8583 specifies a commonmessage interface that allows financial data messages for a transactionto be interchanged between acquirers, issuers, and payment processingnetworks.

In other embodiments, the data in the transaction payload portion 904may be in any suitable format and may include non-financial transactiondata. For example, the transaction payload portion 904 may includenon-financial transaction data including data for alert or notificationgeneration, product information. The transaction payload may be databeing sent between devices, including mobile devices, televisions, pointof sale devices, automobiles.

As depicted in FIG. 9, the location-aware header 902 in the networkprotocol packet 900 is located following the traditional network header902 a. In such embodiments, as the location of the traditional networkheader 902 a is not modified, network devices can process the networkprotocol header 902 a without additional software or configuration dataor changes to the network infrastructure. In alternative embodiments,the location-aware header 902 may be placed preceding the traditionalnetwork header 902 a. In such embodiments, in order to process thenetwork protocol header 900, network devices may require updatedsoftware or configuration data enabling the network devices to recognizethe format of the network protocol packet 900.

FIG. 10 shows a detailed diagram 1000 of the data flow using thelocation-aware infrastructure according to an embodiment of theinvention. FIG. 10 shows the data that may be included in thelocation-aware header portion of the network packet depicted in FIG. 9.The diagram 1000 includes a mobile device 1002, a POS terminal 1006, aPPN mobile network 1010, a payment processing network 1014, a locationterminal 1016, a location proxy 1018, an internet controller 1020, and aprotocol conversion module 1022.

The payment processing network 1014 may further include a PPN servercomputer 1008 to facilitate transaction processing. The internetcontroller 1020 may be a module within the payment processing network1020 and may be operably connected to an authentication module 1020 aand a database 1020 b. The database 1020 b may comprise consumer tables1024 comprising previous data received within the location-aware headeras well as registration and account information associated with theconsumer. The internet controller 1020 may access the consumer tables1024 stored in the database 1020 b. As shown in FIG. 10, the consumertable 1024 may be organized by consumer identifier. In some embodiments,each consumer identifier may have a separate consumer table 1024. In theexample shown in FIG. 10, the consumer identifier is associated with aprofile number, a device identifier, a merchant identifier, and alocation identifier. The data stored in the consumer table 1024 may beused for authentication by the authentication module 1020 a, as well asby the internet controller 1020 for validating transactions.

The internet controller 1020 may validate a transaction by associatingthe data extracted from the location-aware header for the transactionwith a consumer record in the consumer table 1024 using the consumeridentifier and/or device identifier. The consumer record 1024 mayinclude prior location-aware data retrieved from the mobile device 1002and the internet controller may use the relevant prior location-awaredata to validate and/or authenticate a transaction. The internetcontroller may compare the location-aware data associated with thecurrent transaction to the location-aware data stored in the consumertable in order to obtain additional information about the consumer, thetransaction, and their authenticity. This process may be achievedthrough any suitable analysis, as one of ordinary skill in the art wouldunderstand. Additional details and examples are described below withrespect to FIGS. 11 and 12.

C. Methods

Methods according to embodiments of the invention can be described withrespect to FIGS. 5-10.

FIG. 11 is a flowchart describing processing for a network protocolpacket for a non-financial transaction through a system 1000 accordingto an embodiment of the invention. The embodiment described in FIG. 11relates to the issuance of consumer-targeted messages, including, butnot limited to, notification messages, coupons, and alert messages.

In step 1102, a network protocol packet is received, including a networkprotocol header including location-aware data retrieved by a locationterminal in proximity to a mobile device. In embodiments of the presentinvention, the internet controller 1020 in the payment process network1014 may receive the network protocol packet 1018 a. The networkprotocol packet 1018 a may include a merchant identifier, a locationidentifier, a device identifier, the consumer identifier, and atransaction type identifier. In some embodiments of the presentinvention, a transaction data portion may also be included in thenetwork protocol packet 1018 a. For non-financial transactions, thetransaction data portion may not contain any data or may include a flagfor indicating that the transaction is a non-financial transaction.

In some embodiments of the present invention, a location terminal 1016may access data on a mobile device 1002 to retrieve data for the networkprotocol packet 1018 a. The location terminal 1016 may retrieve datafrom the mobile device 1002 when the mobile device 1002 moves intoproximity to the location terminal 1016. The location terminal 1016 mayretrieve the merchant identifier, device identifier, locationidentifier, and consumer identifier from the mobile device 1002.Further, the location terminal may provide a transaction type identifierindicating that the transaction is a non-financial transaction.

The merchant identifier may be a previously assigned identificationnumber for a merchant. In some embodiments, the merchant identifier maybe a numeric or alphanumeric value. The location identifier maycorrespond to a physical address or some other geographic location. Inone embodiment, the location identifier may correspond to an address ofthe merchant location or to a specific area or product group within themerchant location. The device identifier may correspond to an identifierof the mobile device 1002. In one embodiment, the device identifier maycorrespond to data stored on a subscriber identity module (SIM) of themobile device 1002. The consumer identifier may correspond to anidentifier of the consumer associated with the mobile device 1002. Inone embodiment, the consumer identifier may be a digital wallet number,an email address or other consumer data. The merchant identifier,location identifier, device data, and consumer data may be stored in adatabase 1020 b associated with the payment processing network 1014.

The network protocol packet 1016 a generated by the data retrieved bythe location terminal may then be sent to a location proxy 1018. In someembodiments, the location proxy 1018 may determine whether a POSterminal 1006 conducted a transaction with the mobile device 1002. Thelocation proxy 1018 may then send the network protocol packet 1018 a tothe internet controller 1020. In some embodiments, the network protocolpacket 1018 a may be sent across a communications network (e.g., theInternet).

As an example, a consumer with mobile device 1 802 a may be movingthrough a merchant 804 (as shown in FIG. 8). As the mobile device 1 802a moves in the coverage area of location terminal 816 a, the locationterminal 816 a may retrieve data from the mobile device 1 802 a. Themobile device may periodically transmit mobile communication messages(sometimes called a “ping”) that identifies the mobile device identifierand the subscriber identifier to any wireless receiver within itstransmission range. The location terminal 816 may be configured toreceive the periodic mobile communication messages and identify themobile device identifier and the consumer identifier from the message.

The location terminal may have a pre-configured or pre-determinedmerchant data including a merchant identifier identifying the specificmerchant associated with the location terminal. In some embodiments, thelocation terminal may obtain this information from a similar mobilecommunication message from a local merchant device (e.g. POS). Forexample, the merchant identifier may be numeric value, e.g., 11234,which may indicate merchant identifier 11234 which may be associated atthe internet controller 1020 with merchant “Big Box.”

Location data may indicate a specific location associated with themerchant (e.g., “Big Box”) 804 and may include a particular storeaddress as well as in some embodiments, the particular aisle, location,or product group of one of many location terminals within the merchant.The location data (e.g., 005) may be associated with a specific address(e.g., 9000 Main Street, San Francisco, Calif.) of the merchantidentifier (e.g., 11234) associated with the location data (e.g., 005)at the internet controller 1020. Alternatively, the location data may beassociated with a particular area, product grouping, or other geographicregion within a store to indicate a specific location terminal withinthe merchant (e.g., 005-01, indicating location terminal 01 within thestore associated with location 005 of the merchant 11234). All of therelevant information associated with the identifiers may be stored atthe database of the internet controller 1020 to allow the internetcontroller 1020 to identify and associate received data with aparticular merchant, store, location, product grouping, etc. Forexample, location data 005-01 may indicate the location terminalassociated with the “produce aisle” at store location 005 of “Big Box”merchant.

The device data may include a device identifier for mobile device 1 802a The device identifier may be a phone number (e.g., 415-555-1234)associated with mobile device 1 802 a, or may be an international mobilesubscriber identity (e.g., 310155123456789, where the first three digits(“310”) represent the mobile country code, the second three digits(“155”) represent the mobile network code, and the remaining digits(“123456789”) represent the mobile subscription identifier number withinthe mobile network's subscriber base. Any other suitable deviceidentifiers may also be used.

The consumer data may include a consumer identifier that may representidentification data related to the consumer. For example, the consumeridentifier may be an email address (e.g., janedoe@server.com), username, social security number, personal data of the consumer (e.g., name,address, birthdate, etc.), or any other unique user information.

The transaction type data may be used to indicate the type oftransaction associated with the location-aware header. For example, thetransaction type data may be an alphanumeric or numeric value indicatingwhether the transaction is a payment transaction (e.g., purchase ofgoods or services) or a non-payment transaction (e.g., coupon request oraccount balance request). For instance, a payment transaction mayinclude the transaction type identifier of 0001, a location trackingtransaction may include a transaction type identifier of 0002, and aconsumer authentication for access to a secure area may include atransaction type identifier of 0003. Any additional payment andnon-payment transaction types may be implemented as one of ordinaryskill would recognize.

In step 1104, the location-aware header portion is parsed from thenetwork protocol packet. In embodiments of the present invention, theinternet controller 1020 may receive the network protocol packet 1018 aand parse out the location-aware header (902 b as depicted in FIG. 9).The location-aware header portion may include at least one of merchantdata, location data, device data, consumer data, and transaction typedata.

In some embodiments, after identifying the location-aware data from thelocation-aware header portion, the internet controller 1020 may performan authentication process. The internet controller 1020 may utilize anauthentication module 1020 a to authenticate the mobile device 1002. Insome embodiments, the authentication module may authenticate an IMSI(e.g., 310150123456789, in the example above) retrieved from thesubscriber identity module (SIM) received in a device data field 902 b-3in a location-aware header portion of a network protocol packet 900.

The authentication module 1020 a may authenticate the mobile device 1002using the received device identifier (e.g., IMSI 310150123456789). Theauthentication module 1020 a may retrieve a consumer record or entrycorresponding to the consumer identifier received in the location-awareheader. The consumer record may be retrieved from the database 1020 b.The authentication module 1020 a may then determine whether the deviceidentifier associated with the mobile device 1002 is included in thelist of device identifiers previously associated with the consumeridentifier. The list of device identifiers may include all deviceidentifiers associated with the consumer identifier that the internetcontroller 1020 has received with transactions using the location-awareheader.

For example, the authentication module 1020 a may locate the consumerrecord or entry associated with consumer identifier,“janedoe@server.com.” The authentication module 1020 a may locate thedevice identifiers portion of the consumer record and determine whetherIMSI “310150123456789” is included. If the received device identifier ispresent in the consumer record, the authentication module 1020 a maydetermine that the mobile device 1002 may be authenticated and thetransaction may proceed. If the received device identifier is not in theconsumer record, the authentication module 1020 a may determine that themobile device 1002 cannot be authenticated.

In step 1106, the location-aware data is identified within thelocation-aware header portion. In embodiments of the present invention,the internet controller 1020 may extract the data from thelocation-aware header portion. The internet controller 1020 mayassociate the data extracted from the location-aware header intocorresponding portions of a consumer table 1024. The consumer table 1024may include prior location-aware data retrieved from the mobile device1002 and associate it with the consumer.

In step 1108, a consumer-targeted message is retrieved from a databasebased on the location-aware data in the location-aware header portion.In embodiments of the present invention, the internet controller 1020may use data from the location-aware header portion to obtain thelocation-based consumer-targeted message (e.g., coupons, advertisements,deals or other promotional offers) for the user associated with themobile device 1002. The internet controller 1020 may access a database1020 b containing the consumer-targeted message. In other embodiments,the internet controller 1020 may retrieve the consumer-targeted messagefrom a third party.

In embodiments of the invention, the internet controller 1020 may usethe merchant identifier and the location identifier to retrieve aconsumer-targeted message for the merchant or for a specific productsold by the merchant.

For example, the consumer-targeted message in the form of an incentivemay be merchant-based (20% off total purchases at the merchant 804), ormay be product-based based on the location of mobile device 1 802 a(e.g., $5 off vacuum when mobile device 1 802 a is located in proximityto a location terminal 816 a in a household section of the merchant804).

In step 1110, a response message is generated including the retrievedconsumer-targeted message. The internet controller 1020 may thengenerate a response message including the retrieved consumer-targetedmessage. In embodiments of the present invention, the response messagemay be generated in an internet protocol. In other embodiments, theresponse message may be generated in any suitable communicationsprotocol.

In step 1112, the response message including the consumer-targetedmessage is sent to the mobile device. In some embodiments, where theresponse message is generated in the internet protocol, the internetcontroller 1020 may send the response message across a communicationsnetwork, such as the Internet, to the mobile device 1002.

In alternative embodiments, the response message may be sent to theprotocol conversion module 1022. The protocol conversion module 1022 mayencapsulate the response message into a mobile network protocol (e.g.,SS7 or a comparable signaling protocol), as described previously withrespect to FIGS. 2-4. The encapsulated response message may then be sentto the mobile device 1002 through the PPN mobile network 1010. Theencapsulated response message may be then be displayed on the mobiledevice 1002.

FIG. 12 is a flowchart describing processing for a network protocolpacket for a financial transaction through a system 1000 according to anembodiment of the invention

In step 1202, a network protocol packet is received, including a networkprotocol header including location-aware data and a transaction payloadstoring transaction data. In embodiments of the present invention, theinternet controller 1020 in the payment process network 1014 may receivethe network protocol packet 1018 a. The network protocol packet 1018 amay include a merchant identifier, a location identifier, a deviceidentifier, the consumer identifier, and a transaction type identifier.In some embodiments of the present invention, transaction data may alsobe included in the network protocol packet 1018 a in a transactionpayload portion (904 as shown in FIG. 9).

For example, in addition to the data described with respect to FIG. 11,the network protocol packet 900 may include a transaction payload withtransaction data for the financial transaction. The transaction data inthe transaction payload portion may include payment data (e.g., paymentaccount number, consumer address) from the mobile device 1002,transaction amount (e.g., $100), merchant identifier (merchant number11234), and other data required for processing financial transactions.This data may be used for authorization processes performed by thepayment processing network server computer 1008.

In step 1204, the location-aware header portion is parsed from thenetwork protocol packet and location-aware data is identified. Inembodiments of the present invention, the internet controller 1020 mayreceive the network protocol packet 1018 a and parse out thelocation-aware header (902 b as depicted in FIG. 9). The location-awareheader portion 902 b may contain at least one of merchant data, devicedata, consumer data, and transaction type data.

In embodiments of the present invention, the internet controller 1020may extract the data from the location-aware header portion. Theinternet controller may associate the data extracted from thelocation-aware header into corresponding portions of a consumer table1024. The consumer table 1024 may include prior location-aware dataretrieved from the mobile device 1002 and associate it with theconsumer.

In some embodiments, after identifying the location-aware data from thelocation-aware header portion, the internet controller 1020 may performan authentication process. The internet controller 1020 may utilize anauthentication module 1020 a to authenticate the mobile device 1002. Insome embodiments, the authentication module may authenticate an IMSI(e.g., 310150123456789, in the example above) retrieved from thesubscriber identity module (SIM) received in a device data field 902 b-3in a location-aware header portion of a network protocol packet 900. Theauthentication process may be conducted as described above with respectto FIG.

In step 1206, an authorization process is performed for the transactionusing the transaction data. In embodiments of the present invention, thetransaction data sent by the POS terminal 1006 may be parsed from thetransaction payload portion 904 of the network protocol packet 900. Theinternet controller 1020 may send the transaction data to the PPN servercomputer 1008. As described previously, the PPN server computer 1008 maybe configured to perform authorization and clearing and settlementservices related to financial transactions.

In embodiments of the present invention, the authorization process mayinclude sending an authorization request message from PPN servercomputer 1008 to an issuer computer, and receiving an authorizationresponse message indicating a response to the authorization requestmessage (e.g., indicating whether the transaction has been authorized orrejected).

In step 1208, the transaction is validated using the data in thelocation-aware header portion. In embodiments of the present invention,the location-aware data in the location-aware header portion 902 b maybe used to further validate the transaction. The validation process mayinclude identifying a consumer profile in a database associated with theconsumer data from the location-aware header portion 902 b. The consumerprofile may be located in the consumer tables 1024. In embodiments ofthe present invention, the validation process may also include comparingdata stored in the consumer profile with the location-aware data fromthe location-aware header portion 902 b, wherein the transaction isvalidated when the data stored in the consumer profile match thelocation-aware data from the location-aware header portion 902 b.

In such embodiments, the location-aware data may provide improved frauddetection. For example, the internet controller 1020 may analyze theauthorization response message and compare the transaction data withdata stored in the consumer profile in the consumer tables 1024. In someembodiments, based on the merchant identifier, location identifier, anddevice identifier associated with a consumer identifier, a potentiallyfraudulent transaction may be detected.

For example, the internet controller 1020 b may determine from theconsumer tables 1024 that the device identifier associated with themobile device 1002 made a first purchase at a merchant in San Francisco,Calif. and a second purchase an hour later at a merchant in New YorkCity. The internet controller 1020 may use this data to determine thatthe current transaction is fraudulent or suspect as two transactionsusing the same device identifier would likely not be conducted at thetwo different merchants within a short span of time. In another example,a transaction may not be legitimate if the device identifier is notassociated with the consumer identifier of record (e.g., the deviceidentifier for the transaction is not found in the entry for theconsumer identifier stored in the consumer tables 1024).

In another example, internet controller 1020 b may use the deviceidentifier to verify the consumer. The internet controller 1020 b mayevaluate a consumer identifier (e.g. janedoe@server.com), and a deviceidentifier (e.g., 415-555-1234) received in the location aware header.The internet controller 1020 b may access the consumer table 1024 usingthe consumer identifier. If the consumer account of the consumer hasbeen compromised and is being used on a different mobile device 1002,the profile in the consumer table 1024 associated with the consumeridentifier (“janedoe@server.com”) may not have the device identifier forthe mobile device 1002 conducting the transaction. This may be anindication that the transaction in the transaction payload 904 is beingconducted using consumer account data on a mobile device 1002 notassociated with the consumer, which may be indicative of potentialfraud.

In embodiments of the present invention, if the transaction isdetermined to be fraudulent based on the validation against the consumertable 1024 in the database, the internet controller 1020 may decline tovalidate the consumer or the mobile device 1002. In such cases, theinternet controller 1020 may reject the transaction and notify the uservia the mobile device 1002 and the merchant of the rejection.

In step 1210, a validation response message for the transaction isgenerated based on the validation. Based on the validation performed bythe internet controller 1020, a validation response message may begenerated. In some embodiments, if the transaction was validated, thevalidation response message may include the authorization responsemessage from the issuer authorizing the transaction. In suchembodiments, when the transaction is not or cannot be validated by theinternet controller 1020, the validation response message may include anindicator that the transaction could not be validated. The internetcontroller 1020 may send the validation response message to the mobiledevice 1002 and a merchant associated with the transaction.

In step 1212, the validation response message is sent to the mobiledevice. In some embodiments, where the validation response message isgenerated in the internet protocol, the internet controller 1020 maysend the validation response message across a communications network,such as the Internet to the mobile device 1002. In embodiments of thepresent invention, the internet controller 1020 may send the validationresponse message to the mobile device 1002 and a merchant associatedwith the transaction.

In alternative embodiments, the validation response message may be sentto the protocol conversion module 1022. The protocol conversion module1022 may encapsulate the validation response message into a mobilenetwork protocol (e.g., SS7 or a comparable signaling protocol), asdescribed previously with respect to FIGS. 2-4. The encapsulatedvalidation response message may then be sent to the mobile device 1002through the PPN mobile network 1010. The encapsulated response messagemay be then be displayed on the mobile device 1002.

III. Exemplary Apparatuses

The various participants and elements may operate one or more computerapparatuses (e.g., a server computer) to facilitate the functionsdescribed herein. Any of the elements in the figures may use anysuitable number of subsystems to facilitate the functions describedherein. Examples of such subsystems or components are shown in FIG. 13.The subsystems shown in FIG. 13 are interconnected via a system bus1300. Additional subsystems such as a printer 1308, keyboard 1316, fixeddisk 1318 (or other memory comprising computer readable media), monitor1312, which is coupled to display adapter 1310, and others are shown.Peripherals and input/output (I/O) devices, which couple to I/Ocontroller 1302, can be connected to the computer system by any numberof means known in the art, such as serial port 1314. For example, serialport 1314 or external interface 1320 can be used to connect the computerapparatus to a wide area network such as the Internet, a mouse inputdevice, or a scanner. The interconnection via system bus 1300 allows thecentral processor 1306 to communicate with each subsystem and to controlthe execution of instructions from system memory 1304 or the fixed disk1318, as well as the exchange of information between subsystems. Thesystem memory 1304 and/or the fixed disk 1318 may embody a computerreadable medium.

Further, while the present invention has been described using aparticular combination of hardware and software in the form of controllogic and programming code and instructions, it should be recognizedthat other combinations of hardware and software are also within thescope of the present invention. The present invention may be implementedonly in hardware, or only in software, or using combinations thereof.

The software components or functions described in this application maybe implemented as software code to be executed by one or more processorsusing any suitable computer language such as, for example, Java, C++ orPerl using, for example, conventional or object-oriented techniques. Thesoftware code may be stored as a series of instructions, or commands ona computer-readable medium, such as a random access memory (RAM), aread-only memory (ROM), a magnetic medium such as a hard-drive or afloppy disk, or an optical medium such as a CD-ROM. Any suchcomputer-readable medium may also reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

The present invention can be implemented in the form of control logic insoftware or hardware or a combination of both. The control logic may bestored in an information storage medium as a plurality of instructionsadapted to direct an information processing device to perform a set ofsteps disclosed in embodiments of the present invention. Based on thedisclosure and teachings provided herein, a person of ordinary skill inthe art will appreciate other ways and/or methods to implement thepresent invention.

It is understood that the examples and embodiments described herein arefor illustrative purposes only and that various modifications or changesin light thereof will be suggested to persons skilled in the art and areto be included within the spirit and purview of this application andscope of the appended claims. All publications, patents, and patentapplications cited in this patent are hereby incorporated by referencefor all purposes.

One or more features from any embodiment may be combined with one ormore features of any other embodiment without departing from the scopeof the disclosure.

In some embodiments, any of the entities described herein may beembodied by a computer that performs any or all of the functions andsteps disclosed.

Any recitation of “a”, “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary.

The above description is illustrative and is not restrictive. Manyvariations of the invention will become apparent to those skilled in theart upon review of the disclosure. The scope of the invention should,therefore, be determined not with reference to the above description,but instead should be determined with reference to the pending claimsalong with their full scope or equivalents.

All patents, patent applications, publications, and descriptionsmentioned above are herein incorporated by reference in their entiretyfor all purposes. None is admitted to be prior art.

1-10. (canceled)
 11. A method comprising: receiving, by a computer, anetwork protocol packet including a network protocol header and atransaction payload, the network protocol header including alocation-aware header portion, wherein the location-aware header portionincludes location-aware data retrieved by a location terminal inproximity to a mobile device; parsing the location-aware header portionfrom the network protocol packet; identifying the location-aware datawithin the location-aware header portion according to a location-awarenetwork protocol; retrieving a consumer-targeted message from a databasebased on the location-aware data in the location-aware header portion;generating a response message including the consumer-targeted message;and sending the response message including the consumer-targeted messageto the mobile device.
 12. The method according to claim 11, wherein thelocation-aware header portion includes at least one of mobile devicedata, consumer data, merchant data, location data, and transaction typedata.
 13. The method according to claim 11, wherein theconsumer-targeted message is one of a transaction response message, analert message, a notification message, a rewards message, an incentive,or a coupon.
 14. The method according to claim 11, wherein the networkprotocol packet is an internet protocol packet. 15-20. (canceled) 21.The method according to claim 11, wherein the network protocol packet isfor a non-financial transaction.
 22. The method according to claim 21,wherein the network protocol packet comprises a merchant identifier, alocation identifier, a device identifier, a consumer identifier, and atransaction type identifier.
 23. The method according to claim 22,wherein the transaction type identifier comprises an indicator that atransaction is the non-financial transaction.
 24. The method accordingto claim 22, wherein the location identifier comprises a physicaladdress or a geographic location.
 25. The method according to claim 11,wherein the location-aware data comprises an aisle or location within astore of a merchant.
 26. The method according to claim 22, wherein thedevice identifier corresponds to data stored on a subscriber identitymodule (SIM) of the mobile device.
 27. The method according to claim 22,wherein the consumer identifier comprises a digital wallet number or anemail address of a user of the mobile device.
 28. The method accordingto claim 11, wherein the network protocol header comprises an InternetProtocol (IP) header portion amended with the location-aware headerportion.
 29. The method according to claim 11, wherein the mobile deviceperiodically transmits mobile communication messages to the locationterminal, wherein the mobile communication messages comprise a mobiledevice identifier and a subscriber identifier associated with the mobiledevice.
 30. The method according to claim 11, wherein the locationterminal comprises preconfigured or predetermined merchant data.
 31. Acomputer comprising: one or more processors; and a computer readablemedium coupled to the one or more processors, the computer readablemedium comprising code, executable by the one or more processors forimplementing a method comprising: receiving, by the computer, a networkprotocol packet including a network protocol header and a transactionpayload, the network protocol header including a location-aware headerportion, wherein the location-aware header portion includeslocation-aware data retrieved by a location terminal in proximity to amobile device; parsing the location-aware header portion from thenetwork protocol packet; identifying the location-aware data within thelocation-aware header portion according to a location-aware networkprotocol; retrieving a consumer-targeted message from a database basedon the location-aware data in the location-aware header portion;generating a response message including the consumer-targeted message;and sending the response message including the consumer-targeted messageto the mobile device.
 32. The computer according to claim 31, whereinthe location-aware header portion includes at least one of mobile devicedata, consumer data, merchant data, location data, and transaction typedata.
 33. The computer according to claim 31, wherein theconsumer-targeted message is one of a transaction response message, analert message, a notification message, a rewards message, an incentive,or a coupon.
 34. A system comprising: a computer comprising: one or moreprocessors; and a computer readable medium coupled to the one or moreprocessors, the computer readable medium comprising code, executable bythe one or more processors for implementing a method comprising:receiving, by the computer, a network protocol packet including anetwork protocol header and a transaction payload, the network protocolheader including a location-aware header portion, wherein thelocation-aware header portion includes location-aware data retrieved bya location terminal in proximity to a mobile device; parsing thelocation-aware header portion from the network protocol packet;identifying the location-aware data within the location-aware headerportion according to a location-aware network protocol; retrieving aconsumer-targeted message from a database based on the location-awaredata in the location-aware header portion; generating a response messageincluding the consumer-targeted message; and sending the responsemessage including the consumer-targeted message to the mobile device.35. The system according to claim 34, wherein the location-aware headerportion includes at least one of mobile device data, consumer data,merchant data, location data, and transaction type data.
 36. The systemaccording to claim 34, wherein the consumer-targeted message is one of atransaction response message, an alert message, a notification message,a rewards message, an incentive, or a coupon.